Re: Intent to ship: OpenType Variation Font support

Hi Jonathan, This led me to believe something isn't completely hooked up on > further experimentation, though, I find that it does work as expected if > the font is loaded from a @font-face resource with the appropriate > descriptors. So this seems to be only a limitation for installed fonts?

Re: FYI: Short Nightly Shield Study involving DNS over HTTPs (DoH)

On 3/21/18 9:04 AM, Axel Hecht wrote: > I have a couple of further questions: > > One is about the legal impact on users. DNS mangling is part of law > enforcement strategies in many parts of the world (incl Germany). Would you mind describing this in more detail? What kind of DNS mangling do

Re: FYI: Short Nightly Shield Study involving DNS over HTTPs (DoH)

On 3/21/18 10:53 AM, tom...@gmail.com wrote: On Wednesday, March 21, 2018 at 3:30:48 PM UTC+1, Boris Zbarsky wrote: The point is to gather data on how this behaves in the wild. If the study is opt-in, then you have to try to figure out what part of the effect you're seeing (if any) is just

Re: FYI: Short Nightly Shield Study involving DNS over HTTPs (DoH)

I have a couple of further questions: One is about the legal impact on users. DNS mangling is part of law enforcement strategies in many parts of the world (incl Germany). We should restrict this experiment to regions where Mozilla knows that there's no legal trouble of using DoH and

Re: FYI: Short Nightly Shield Study involving DNS over HTTPs (DoH)

On Wednesday, March 21, 2018 at 3:30:48 PM UTC+1, Boris Zbarsky wrote: > The point is to gather data on how this behaves in the wild. If the > study is opt-in, then you have to try to figure out what part of the > effect you're seeing (if any) is just selection effects. >From my understanding

Re: FYI: Short Nightly Shield Study involving DNS over HTTPs (DoH)

On 3/21/18 10:02 AM, tom...@gmail.com wrote: I also don't see any arguments why this *needs* to be opt-out? The point is to gather data on how this behaves in the wild. If the study is opt-in, then you have to try to figure out what part of the effect you're seeing (if any) is just

Re: FYI: Short Nightly Shield Study involving DNS over HTTPs (DoH)

On Tuesday, March 20, 2018 at 3:35:48 AM UTC+1, Kris Maglione wrote: > >Let me add my voice as a person outside the network team who can understand > >the concerns and _still thinks we should be doing this_. > > I'll second this. > > I think it's reasonable to be concerned about the public

Re: Use cases for invalid-Unicode atoms

> I'll go ahead with doing WHATWG-compliant "with replacement" when > trying to atomize invalid UTF-8 (which shouldn't happen anyway). For code archeologists: Don't believe what I said upthread about non-atomic empty-string atoms. My code reading was evidently wrong considering that we have test

Re: Use cases for invalid-Unicode atoms

On Wed, Mar 21, 2018 at 11:40 AM, Anne van Kesteren wrote: > On Wed, Mar 21, 2018 at 10:27 AM, Henri Sivonen wrote: >> * A bunch of things atomicize URL components. I'd hope that the URLs >> were converted from UTF-16 to UTF-8 at some prior point ensuring

Re: FYI: Short Nightly Shield Study involving DNS over HTTPs (DoH)

+1 (as a Moz fan and privacy expert) On Tue, Mar 20, 2018 at 2:35 AM, Kris Maglione wrote: > On Mon, Mar 19, 2018 at 07:27:39PM -0700, Nicholas Alexander wrote: >> >> Hi all, >> >> On Mon, Mar 19, 2018 at 3:56 PM, Xidorn Quan wrote: >> >>> It's fine to

Re: Intent to ship: OpenType Variation Font support

On 21/03/2018 08:03, dr...@chromium.org wrote: font-{weight,stretch,style} are parsed and hooked up to the variable fonts rasterization backend since we initially shipped OpenType Variations in M62. I implemented this in Blink, so if you are observing any issues, mind sharing them? I'd be

Re: Use cases for invalid-Unicode atoms

On Wed, Mar 21, 2018 at 10:27 AM, Henri Sivonen wrote: > * A bunch of things atomicize URL components. I'd hope that the URLs > were converted from UTF-16 to UTF-8 at some prior point ensuring UTF-8 > validity, but it's hard to be sure. At least per the specification all

Re: Use cases for invalid-Unicode atoms

On Tue, Mar 20, 2018 at 8:22 PM, Steve Fink wrote: > On 03/20/2018 06:49 AM, Henri Sivonen wrote: >> >> On Tue, Mar 20, 2018 at 12:44 PM, Henri Sivonen >> wrote: >>> >>> On Tue, Mar 20, 2018 at 11:12 AM, Henri Sivonen >>> wrote:

Re: Intent to ship: OpenType Variation Font support

Hi Jonathan, On Tuesday, March 20, 2018 at 1:16:42 PM UTC+2, Jonathan Kew wrote: > (Note that Blink also hasn't fully implemented this, at least judging by > testing of Chrome stable: they have done the CSS parsing extensions, but > not hooked it up to the rendering side. Maybe that's in