In response to Silvia's comments—
I think relying on is a pretty good result, I think we need to
stretch further.
An is a piece of content that isn't semantically defined on its
parents. (right?)
Shouldn't we have a way to define this without confusing the "main" content of
the 'page'?
"Skip to main" isn't the only use case :-)
FYI, as a web designer, (slap me here) I've almost never designed in a "skip to
main" link.
Call me ignorant (probably fitting), but in the "real world" a new way to
markup 'skip to main' isn't on my mind.
What does concern me, as a web builder, *eve
Steve, you never fail to amaze me. (Thank you!)
So, with it laid out as clearly as that, the glaringly obvious missing element
is . (Thank you Simon)
Over to you, @Hixie.
On 08/11/2012, at 1:53 AM, Steve Faulkner wrote:
> Hi Ben,
>
> I generally markup pages using ARIA roles:
>
>
>
>
I generally markup pages using ARIA roles:
and variations thereafter—
If there were to be a attribute (with an implicit ARIA role to match),
where would it end? ?
What is to be gained by adding an element, rather than using ARIA roles? Isn't
that what ARIA is designed for?
On 08/11/
Tab, Thanks for going to effort of providing some clear and detailed notes
about this.
I think the rest of the committee could learn from this account, and perhaps
consider theres a lot more to communication than editing a live-spec and
dumping it into the mailing list.
On 22/05/2012, at 10
Non announcement _here_ is one thing, sure; but as those aiming to plan, test
and measure different approaches, it's your role to research other developments
out side of the WHATWG bubble.
WHATWG does not exist to be a closed society.
On 17/05/2012, at 6:46 PM, Maciej Stachowiak wrote:
>
>
nd implement an integration experience
On Monday, 18 July 2011 at 9:10 AM, Bjartur Thorlacius wrote:
> Þann sun 17.júl 2011 22:46, skrifaði Ben Schwarz:
> >
> > 3)
> > As a web designer / developer
> > I want to be able to ascertain if another website has registered a
After recently discovering custom protocol handlers[1], it struck me that it
would be difficult to provide a decent user experience for those who used
browsers which did not support the feature.
There have been previous calls to add further methods to the custom protocol
ecosystem, such as a mo
t;whatwg/w3c in an effort to extend the current scope of
>localStorage/sessionStorage.
I'm looking for feedback and discussion that will aid the HTML5 storage
specification, with real software as a form of user requirement, rather than
imagination.
Cheers,
Ben Schwarz
--
+ germanforblack.com
+ ab-c.com.au
>
>
> On Mon, August 9, 2010 02:59, Ben Schwarz wrote:
> > Because you can find an example isn't exactly what I would call a "use
> > case".
>
> I didn't find "an example", I found many - more than one of which I
> quoted, by way of
've highlighted here, rather than
shoehorning it in.
Is there someone on this list who feels passionately enough to make some
working examples and demos?
On Mon, Aug 9, 2010 at 11:42 AM, Andy Mabbett wrote:
> On Mon, August 9, 2010 02:19, Ben Schwarz wrote:
> > While creating an input
While creating an input that works for every use case you can think of
sounds like a good idea, I'd like to question weather a user would ever *enter
a date* that would require the inclusion of BC/AD.
I'm certain that there is a requirement to markup such text, but as for *
entry* I'm strongly of
I'm really not too sure what pre-existing problem this actually solves.
Given that a server sets the correct mime-types for a given resource, we
know what "type" it is already.
Setting the Content-disposition on the client side creates an annoying user
experience.
If I want to open a link in a ne
Hi All,
I'm sure link relations have already had many debates around how they should
work and the exact use case that they cover.
I'd like to add another card to the deck :-)
When using link relations on an "a" tag, one would find it useful to have
"next" and "previous" link relations, this is e
14 matches
Mail list logo
