On Tue, 31 Jan 2012, Robert O'Callahan wrote:
> On Tue, Jan 31, 2012 at 11:10 AM, Ian Hickson wrote:
> >
> > Is there any reason you can't just put whatever styles you want into a
> >
On Tue, Jan 31, 2012 at 11:10 AM, Ian Hickson wrote:
> Is there any reason you can't just put whatever styles you want into a
>
On Mon, Jan 30, 2012 at 1:54 PM, Ian Hickson wrote:
> On Tue, 8 Nov 2011, Ojan Vafai wrote:
>> We keep running into the use case where the physical position matters
>> for the tab order. The problem with just setting tabIndex (or CSS3
>> tab-index) is that it takes the thing out of the natural ord
On Mon, 30 Jan 2012, Erik Arvidsson wrote:
> On Mon, Jan 30, 2012 at 13:54, Ian Hickson wrote:
> > Surely that would be better than having authors manage local regions
> > for tabindex, especially since the positioning depends on the CSS
> > level, not the HTML level, and thus trying to manage t
On Mon, Jan 30, 2012 at 13:54, Ian Hickson wrote:
> Surely that would be better than having authors manage local regions for
> tabindex, especially since the positioning depends on the CSS level, not
> the HTML level, and thus trying to manage the tabindex in the HTML would
> be a layering violati
On Wed, 16 Nov 2011, Ian Hickson wrote:
> On Wed, 16 Nov 2011, Gavin Kistner wrote:
> >
> > Can you provide an example in script of when the "found specs" would
> > apply, and when the "other specs" would apply?
>
> Hmm, good point. Now that we're using CORS explicitly, all of the stuff
> about
On Wed, 15 Jun 2011, Jukka K. Korpela wrote:
> 2011-06-15 3:26, Ian Hickson wrote:
> >
> > Styling a whole document by having style sheets in the middle of the
> > document causes flickering (as the browser updates the styles), and is
> > hard to maintain. So we make this non-conforming, to help
On Thu, 10 Nov 2011, Robert O'Callahan wrote:
>
> http://www.whatwg.org/specs/web-apps/current-work/#read-media
>
> Can we allow the UA to add custom vendor-prefixed attributes to the
> and/or elements? Alternatively, a vendor-prefixed class?
> We want to be able to use a style sheet with rules
On Tue, 8 Nov 2011, Francis Boumphrey wrote:
>
> Why does the (Editor's Draft 4 November 2011) spec not specifically
> allow the 'autoplay' element? It has been supported by most browsers for
> at least 10 years, and is specified on the and elements,
I assume you mean the autoplay="" attribute
On Tue, 8 Nov 2011, Ojan Vafai wrote:
>
> We keep running into the use case where the physical position matters
> for the tab order. The problem with just setting tabIndex (or CSS3
> tab-index) is that it takes the thing out of the natural order.
>
> This problem comes up in a lot of places (e.g
Le 17 janv. 2012 à 19:51, Boris Zbarsky a écrit :
> On 1/17/12 7:37 PM, Tab Atkins Jr. wrote:
>> SPDY push allows the server to send down additional resources along
>> with the main resource
[…]
> Ah, ok. Yeah, there's obviously no way the client can prevent that, nor
> should it try.
"no way
Le 17 janv. 2012 à 19:37, Tab Atkins Jr. a écrit :
> SPDY push allows the server to send down additional resources along
> with the main resource, before the client actually requests them.
When you say "additional resources". Is that "from the same domain"?
--
Karl Dubost - http://dev.opera.
On Mon, 7 Nov 2011, Jonas Sicking wrote:
> On Wed, Mar 23, 2011 at 5:37 PM, Ian Hickson wrote:
> >
> > I'm studying some of the feedback raised over the past few months
> > regarding history.pushState() and related APIs, in particular in the
> > context of applying these changes to the spec:
> >
>
Just to make sure I understand the proposal correctly : if allow-popups is
specified and a new
browsing context is being created, this inherits the sandbox flags of the
document
creating the new popup/browsing context ?
This does seem to complicate the algorithm to determine if a navigation is
14 matches
Mail list logo
