http://www.w3.org/TR/html-markup/th.html#th.attrs.scope Says nothing
about what a UA should do by default, nor when scope can be omitted
due to such defaults.
I suggest explicitly defining defaults for the benefit of both UAs and
HTML authors. I would expect the defaults to be defined something
Nicholas Shanks cont...@nickshanks.com, 2012-10-01 09:53 +0100:
http://www.w3.org/TR/html-markup/th.html#th.attrs.scope Says nothing
about what a UA should do by default, nor when scope can be omitted
due to such defaults.
Don't look to that document for any information about default UA
On 1 October 2012 10:21, Michael[tm] Smith m...@w3.org wrote:
Don't look to that document for any information about default UA behavior,
or anything at all about UA processing behavior. I tried to make that very
clear in the abstract and intro for that document.
Sorry, I never saw that:
Nicholas Shanks cont...@nickshanks.com, 2012-10-01 12:04 +0100:
https://encrypted.google.com/search?q=html5+default+header+scope
for me, returned:
Coding An HTML 5 Layout From Scratch | Smashing Coding
coding.smashingmagazine.com/.../designing-a-html-5-layout-from-sc...
HTML th scope
Nicholas Shanks cont...@nickshanks.com, 2012-10-01 09:53 +0100:
[...]
I suggest explicitly defining defaults for the benefit of both UAs and
HTML authors. I would expect the defaults to be defined something like
this:
Rule 1) If a row begins with zero or more empty TD elements, followed
by
Summary: I've changed rel=noreferrer so that when it creates a new
top-level browsing context, it doesn't clone sessionStorage. Turns out
that as specced, it already did everything else that was needed.
On Wed, 6 Jun 2012, Charlie Reis wrote:
I've posted a new proposal to the WhatWG wiki to
On Mon, Oct 1, 2012 at 5:10 PM, Ian Hickson i...@hixie.ch wrote:
+ have the new page be in a new browsing context
...it's a new browsing context (e.g. target=_blank).
I'm not very familiar with the browsing context concept: what's the
practical security issue here? It should never be
On 10/1/12 6:10 PM, Ian Hickson wrote:
On Tue, 19 Jun 2012, Boris Zbarsky wrote:
On 6/19/12 1:56 PM, Charlie Reis wrote:
That's from the [if] the user agent determines that the two browsing
contexts are related enough that it is ok if they reach each other
part, which is quite vague.
This
On Mon, 1 Oct 2012, Glenn Maynard wrote:
On Mon, Oct 1, 2012 at 5:10 PM, Ian Hickson i...@hixie.ch wrote:
+ have the new page be in a new browsing context
...it's a new browsing context (e.g. target=_blank).
I'm not very familiar with the browsing context concept: what's the
On Mon, Oct 1, 2012 at 8:37 PM, Ian Hickson i...@hixie.ch wrote:
The all-too-common bad reason is we want people to keep pages open in
the user's browser for long as possible in the hopes that it'll make
them come back by accident, so we'll sprinkle target=_blank everywhere,
eg.
10 matches
Mail list logo