History.pushState() could wipe the busy
flag, but that might be the wrong thing to do if a busy part of your UI
stays there.
Also: what does the busy indicator do in fullscreen?
I'm not trying to shoot this down, just pointing at potential pitfalls
to avoid adding a feature that will j
; LD would allow you to pin a ticket you've
bought in such a way that it displays just the essential time/location
information you want to see at a glance. The use cases are totally
different.
--
Robin Berjon - http://berjon.com/ - @robinberjon
___
for images, View
Description is only afforded if there is a longdesc attribute. Honestly,
I'm not sure how many people know that who aren't either on this list or
involved in standards somehow.
--
Robin Berjon - http://berjon.com/ - @robinberjon
_
On 22/09/2014 15:04 , Henri Sivonen wrote:
On Mon, Sep 22, 2014 at 3:48 PM, Robin Berjon wrote:
On 22/09/2014 14:40 , Henri Sivonen wrote:
If that was the goal, changing the "Goals" section of the spec to cast
doubts about whether the direction the W3C envisions for the spec is
On 22/09/2014 14:40 , Henri Sivonen wrote:
On Mon, Sep 22, 2014 at 2:41 PM, Robin Berjon wrote:
I was hoping that we could simply reference WHATWG URL as a (small) token of
good faith and normalisation, adding a small cobblestone to pave the way to
cooperation.
If that was the goal, changing
n this space are very welcome (I'll be trying some stuff in
my corner, which I'll make available soon).
--
Robin Berjon - http://berjon.com/ - @robinberjon
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
HTML5 out of the door: it frees up a
lot of flexibility (and energy) in how things are done from now on.
Constructive input is certainly welcome :)
--
Robin Berjon - http://berjon.com/ - @robinberjon
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
attempt at fixing the issues
you see with the group then you can certainly distance yourself from the
group's actions.
But if you haven't tried to change things constructively, complaining
about it elsewhere doesn't seem all that helpful.
--
Robin Berjon - http://ber
n that we don't have the
hindsight to evaluate it much.
Unless you're thinking of XHTML Modularisation. But that would be like
blaming Mozilla for : not entirely fair :)
--
Robin Berjon - http://berjon.com/ - @robinberjon
___
dev-platfor
uried, and zombified a few times over. Mentioning it in your
review (as several others have done already) would already carry weight
(and wouldn't cost you the trouble that entering the fray otherwise might).
Thanks!
--
Robin Berjon - http://berjon.com/
and people are thinking about the problem, so if
it's solvable in an acceptable way I don't why it wouldn't eventually
work out.
http://discourse.specifiction.org/t/element-queries/26
--
Robin Berjon - http://berjon.com/ - @robinberjon
group can change whenever it wants to.
Putting it in the charter can be a nice way of documenting it (and
helping with enforcement), but it isn't really binding.
--
Robin Berjon - http://berjon.com/ - @robinberjon
___
dev-platform mailing li
ink you'll be better off speaking directly to the group's chairs and
team contacts than bringing further feedback into WBS.
--
Robin Berjon - http://berjon.com/ - @robinberjon
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
or user control here, so as to keep things simple.
IMHO the only question is whether that would break content and possibly
require a spec change. I suspect not for content; on the spec side it
already says that UAs don't have to support it.
--
Robin Berjon - http://berjon
14 matches
Mail list logo
