Re: [whatwg] Outline style to use for drawSystemFocusRing

2014-01-07 Thread Dominic Mazzoni
On Tue, Jan 7, 2014 at 9:18 PM, Rik Cabanier wrote: > > On Tue, Jan 7, 2014 at 1:10 PM, Ian Hickson wrote: > >> >> > I don't see that as an argument against caching the last known location >> > of an object too. >> >> If you want to store state, that's what addHitRegion() is for. It's the >> ret

Re: [whatwg] Outline style to use for drawSystemFocusRing

2014-01-07 Thread Rik Cabanier
On Tue, Jan 7, 2014 at 9:45 PM, Ian Hickson wrote: > On Tue, 7 Jan 2014, Rik Cabanier wrote: > > On Tue, Jan 7, 2014 at 1:10 PM, Ian Hickson wrote: > > > > > > > I don't see that as an argument against caching the last known > > > > location of an object too. > > > > > > If you want to store sta

Re: [whatwg] Outline style to use for drawSystemFocusRing

2014-01-07 Thread Dominic Mazzoni
On Tue, Jan 7, 2014 at 1:10 PM, Ian Hickson wrote: > If the user needs a big ring, it seems bad for us not to render one. > Especially since we can know this. > Yes, there are users who need extra high-contrast focus rings. But no, they don't get that from an operating system setting that the a

Re: [whatwg] Outline style to use for drawSystemFocusRing

2014-01-07 Thread Ian Hickson
On Tue, 7 Jan 2014, Rik Cabanier wrote: > On Tue, Jan 7, 2014 at 1:10 PM, Ian Hickson wrote: > > > > > I don't see that as an argument against caching the last known > > > location of an object too. > > > > If you want to store state, that's what addHitRegion() is for. It's > > the retained mode

Re: [whatwg] Outline style to use for drawSystemFocusRing

2014-01-07 Thread Rik Cabanier
On Tue, Jan 7, 2014 at 1:10 PM, Ian Hickson wrote: > > > I don't see that as an argument against caching the last known location > > of an object too. > > If you want to store state, that's what addHitRegion() is for. It's the > retained mode API for canvas. The draw*FocusRing() methods are direc

Re: [whatwg] Simplified element draft

2014-01-07 Thread Kornel LesiƄski
On Sat, 04 Jan 2014 06:36:27 -, Adam Barth wrote: In order for the HTMLPreloadScanner to issue preload requests for elements, the HTMLPreloadScanner would need to be able to evaluate arbitrary media requests. That's difficult to do without joining the main thread because the media query e

Re: [whatwg] Simplified element draft

2014-01-07 Thread Yoav Weiss
On Tue, Jan 7, 2014 at 11:13 PM, Tab Atkins Jr. wrote: > On Tue, Jan 7, 2014 at 1:53 PM, Boris Zbarsky wrote: > > On 1/7/14 4:28 PM, Yoav Weiss wrote: > >> Since this case is not the majority case, we could bail out of it by > >> delaying the iframe's subresource loading that rely on viewport > >

Re: [whatwg] Simplified element draft

2014-01-07 Thread Tab Atkins Jr.
On Tue, Jan 7, 2014 at 1:53 PM, Boris Zbarsky wrote: > On 1/7/14 4:28 PM, Yoav Weiss wrote: >> Since this case is not the majority case, we could bail out of it by >> delaying the iframe's subresource loading that rely on viewport >> dimensions until the parent's layout is considered "done" > > Th

Re: [whatwg] Simplified element draft

2014-01-07 Thread Boris Zbarsky
On 1/7/14 4:28 PM, Yoav Weiss wrote: Since this case is not the majority case, we could bail out of it by delaying the iframe's subresource loading that rely on viewport dimensions until the parent's layout is considered "done" That seems fairly undesirable, actually, though limiting it only to

Re: [whatwg] Simplified element draft

2014-01-07 Thread Yoav Weiss
On Tue, Jan 7, 2014 at 6:20 PM, Boris Zbarsky wrote: > On 1/7/14 12:01 PM, Yoav Weiss wrote: > >> I'd love to get some more details regarding that. I'll start a >> mozilla.dev.platform thread on the subject, since it's Gecko specific. >> > > It's actually not entirely Gecko-specific. > > Consider

Re: [whatwg] Outline style to use for drawSystemFocusRing

2014-01-07 Thread Ian Hickson
On Wed, 16 Oct 2013, Dominic Mazzoni wrote: > On Wed, Oct 16, 2013 at 12:46 PM, Ian Hickson wrote: > > WCAG 2.0 claims that "many platforms allow the user to customize the > > rendering of this focus indicator", though I admit that I don't see > > any references for this claim: > > > >http:/

Re: [whatwg] Simplified element draft

2014-01-07 Thread Boris Zbarsky
On 1/7/14 3:06 PM, Boris Zbarsky wrote: 4) IE11 seems to do what Blink/WebKit do. To test this, you'll need a testcase more like: div { color: purple; } @media (min-width: 300px) { #one { color: yellow; } } @media (max-width: 300px) { #two { color: yellow; } } -Boris

Re: [whatwg] Simplified element draft

2014-01-07 Thread Boris Zbarsky
On 1/7/14 2:24 PM, Ian Hickson wrote: It's probably just a matter of saying, in the rendering section, that nested browsing contexts that aren't _being_rendered_ (or that are s outside s) get a 0x0 viewport. That doesn't seem unreasonable. (Viewports that are being rendered seem to have an u

Re: [whatwg] Simplified element draft

2014-01-07 Thread Ian Hickson
On Tue, 7 Jan 2014, Boris Zbarsky wrote: > On 1/7/14 12:01 PM, Yoav Weiss wrote: > > I'd love to get some more details regarding that. I'll start a > > mozilla.dev.platform thread on the subject, since it's Gecko specific. > > It's actually not entirely Gecko-specific. > > Consider a display:non

Re: [whatwg] Simplified element draft

2014-01-07 Thread Boris Zbarsky
On 1/7/14 12:01 PM, Yoav Weiss wrote: I'd love to get some more details regarding that. I'll start a mozilla.dev.platform thread on the subject, since it's Gecko specific. It's actually not entirely Gecko-specific. Consider a display:none iframe. How should viewport-size-related media querie

Re: [whatwg] Simplified element draft

2014-01-07 Thread Yoav Weiss
On Mon, Jan 6, 2014 at 6:47 PM, Boris Zbarsky wrote: > On 1/6/14 12:42 PM, Yoav Weiss wrote: > >> I don't know much about Gecko's implementation of the preloader, so I >> could be wrong, but from looking at nsHtml5TreeOpExecutor, it seems like >> in Gecko (similarly to current Blink) the preloade