Hi Tim,
Are you saying we should not introduce a main element...
I don't believe I ever said anything about not introducing a
mainelement. I'm very much on the fence about it. I've been trying
to carefully
balance the pros and cons to avoid a biased judgement. Here are some of
what I've
On Thu, Nov 15, 2012 at 12:59 PM, Tim Leverett ...@gmail.com wrote:
Personally, I'd rather see main be more about marking up content in
general, such as in this example which is invalid given the current state
of the spec:
article id=1
header /
main /
footer /
/article
article
On Thu, Nov 15, 2012 at 7:27 PM, Ian Yang i...@invigoreight.com wrote:
On Thu, Nov 15, 2012 at 12:59 PM, Tim Leverett ...@gmail.com wrote:
Personally, I'd rather see main be more about marking up content in
general, such as in this example which is invalid given the current state
of the
On Wed, Nov 14, 2012 at 11:05 AM, Boris Zbarsky bzbar...@mit.edu wrote:
I believe Gecko simply stores the original string (lowercased), modulo IDN
stuff. Since this works for both DNS names and IP addresses, a requirement
that some other representation be stored is actually a bit of an
On Wed, Nov 14, 2012 at 8:07 PM, Fred Andrews freda...@live.com wrote:
The canvas that scripts draw into could be over-sized with the UA down
sampling this to
fit the target size and taking into account the sub-pixel screen layout
when doing so.
Obviously, that would be costly (x3 pixels),
Con: Adding a main element adds redundancy to the [role=main]
attribute.
I don't see why this is a con, if main is mapped to role=main in the
browser it means that authors won't have to. Also adding
aside/article/footer etc adds redundancy to the matching ARIA roles.
Redundancy tends to be a
On 11/15/12 5:45 AM, Anne van Kesteren wrote:
Well and it is validated. You definitely parse the string
Yes, absolutely.
but I can
see how that is cheaper than transforming the string. And that string
is then passed to the DNS layer?
I don't know offhand. I'd have to go dig...
We could
Con: Adding a main element adds redundancy to the [role=main]
attribute.
I don't see why this is a con, if main is mapped to role=main in the
browser it means that authors won't have to. Also adding
aside/article/footer etc adds redundancy to the matching ARIA roles.
Redundancy tends to be a
To post feedback to the WHATWG list, please subscribe first (and post
from the same e-mail address as you subscribed from). We require this
because of the level of spam the list would otherwise receive.
If you just want to submit drive-by feedback and aren't concerned
about receiving a reply, you
On Fri, Nov 16, 2012 at 1:45 AM, Tim Leverett ...@gmail.com wrote:
Con: Adding a main element adds redundancy to the [role=main]
attribute.
I don't see why this is a con, if main is mapped to role=main in the
browser it means that authors won't have to. Also adding
aside/article/footer
I think I can do it for WebKit if WHATWG specification and W3C
specification are changed so.
On Thu, Nov 15, 2012 at 2:23 AM, Mounir Lamouri mou...@lamouri.fr wrote:
On 13/11/12 09:42, TAMURA, Kent wrote:
The current UI implementations of Opera, iOS, and Chrome-Android spoil
the
HTML
Thanks Tobie, that does sound related, but not quite the same use case.
That proposal seems to want to make the creation of memory/network/runtime
performance profiles scriptable if the user allows it. Presumably you
wouldn't do that routinely, which raises the question of when you would do
it.
On 15 November 2012 19:20, Silvia Pfeiffer silviapfeiff...@gmail.com wrote:
On Fri, Nov 16, 2012 at 1:45 AM, Tim Leverett ...@gmail.com wrote:
Con: Adding a main element adds redundancy to the [role=main]
attribute.
I don't see why this is a con, if main is mapped to role=main in the
On Thu, Nov 15, 2012 at 8:21 PM, Eitan Adler li...@eitanadler.com wrote:
Actually, there's a good point: I would actually add this: if main or
an
element with @role=main exist on the page, there is no need to run the
Scooby-Doo algorithm and that element can just be chosen as the main
On Fri, Nov 16, 2012 at 12:21 PM, Eitan Adler li...@eitanadler.com wrote:
On 15 November 2012 19:20, Silvia Pfeiffer silviapfeiff...@gmail.com
wrote:
On Fri, Nov 16, 2012 at 1:45 AM, Tim Leverett ...@gmail.com wrote:
Con: Adding a main element adds redundancy to the [role=main]
What if both exist but are different elements?
Favor the first or most ancestral occurrence.
I concur.
☺
On Thu, Nov 15, 2012 at 8:48 PM, Hugh Guiney hugh.gui...@gmail.com wrote:
On Thu, Nov 15, 2012 at 8:21 PM, Eitan Adler li...@eitanadler.com wrote:
Actually, there's a good point: I
Are setCapture/releaseCapture specified on document anywhere? The last
thing I see about it is
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2008-November/017415.html
and then nothing...
Note that I suspect we do need a releaseCapture() so pages can call it
without throwing, even if
17 matches
Mail list logo
