On Wed, Jul 24, 2013 at 12:45 AM, Ian Hickson i...@hixie.ch wrote:
If the options are:
- authors never use the feature
- users lose their control over their browser
- the feature has a complicated API
...then we're stuck in a bad place, certainly. But I don't think those are
the only
On Mon, 31 Dec 2012, Jonas Sicking wrote:
On Fri, Dec 28, 2012 at 11:07 PM, Ian Hickson i...@hixie.ch wrote:
On Fri, 28 Dec 2012, Jonas Sicking wrote:
I don't think it's a good solution to leave it undefined if
all/none/some of the UA menuitems are displayed by default. While it
on an
On Wed, Jan 9, 2013 at 10:17 PM, Ian Hickson i...@hixie.ch wrote:
Optimising for the short-term shim author's experience rather than the
long-term HTML authoring experience seems backwards to me.
After input from a couple of other Gecko developers, I withdraw my
objection to menuitem being
On Sat, Dec 29, 2012 at 3:23 AM, Ian Hickson i...@hixie.ch wrote:
* menuitem is void (requires parser changes).
* command is entirely gone. (Actually, I renamed command to menuitem
and made it so it's only allowed in menu.)
Did you actually make these changes to the parsing algorithm? It
On 1/4/13 7:05 PM, L. David Baron wrote:
I feel that I do see this quite often. maps.google.com, Google docs,
and Zimbra are three examples off the top of my head that I spend a
lot of time with.
Has anyone asked the authors of these sites if they would have liked
to retain the browser's
On Sat, Dec 29, 2012 at 10:17 AM, David Young dyo...@pobox.com wrote:
On Sat, Dec 29, 2012 at 01:23:20AM +, Ian Hickson wrote:
On Sun, 23 Oct 2011, Eric Sh. wrote:
I was trying out the HTML5 context menu in firefox and I saw that there
is no way(in the specs) to create an empty menu
On Fri, Jan 4, 2013 at 3:34 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Sat, Dec 29, 2012 at 10:17 AM, David Young dyo...@pobox.com wrote:
On Sat, Dec 29, 2012 at 01:23:20AM +, Ian Hickson wrote:
On Sun, 23 Oct 2011, Eric Sh. wrote:
I was trying out the HTML5 context menu in
On Fri, Jan 4, 2013 at 4:56 PM, Ian Hickson i...@hixie.ch wrote:
On Fri, 4 Jan 2013, Jonas Sicking wrote:
Gah, strongly agree. Simple example - I use Back constantly in the
context menu, and would be really pissed if pages could easily kill
that. [...]
Can you elaborate on what you
On Fri, Jan 04, 2013 at 03:34:11PM -0800, Tab Atkins Jr. wrote:
On Sat, Dec 29, 2012 at 10:17 AM, David Young dyo...@pobox.com wrote:
On Sat, Dec 29, 2012 at 01:23:20AM +, Ian Hickson wrote:
On Sun, 23 Oct 2011, Eric Sh. wrote:
I was trying out the HTML5 context menu in firefox and
On Friday 2013-01-04 16:52 -0800, Jonas Sicking wrote:
On Fri, Jan 4, 2013 at 3:34 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Mon, Dec 31, 2012 at 12:54 AM, Jonas Sicking jo...@sicking.cc wrote:
What I was saying as a browser vendor is that I don't think that
authors are going to use
On Fri, 4 Jan 2013, Jonas Sicking wrote:
On Fri, Jan 4, 2013 at 4:56 PM, Ian Hickson i...@hixie.ch wrote:
On Fri, 4 Jan 2013, Jonas Sicking wrote:
Gah, strongly agree. Simple example - I use Back constantly in
the context menu, and would be really pissed if pages could easily
On Fri, Dec 28, 2012 at 11:07 PM, Ian Hickson i...@hixie.ch wrote:
On Fri, 28 Dec 2012, Jonas Sicking wrote:
I don't think it's a good solution to leave it undefined if
all/none/some of the UA menuitems are displayed by default. While it on
an API level won't break anything, authors consider
On Sat, Dec 29, 2012 at 01:23:20AM +, Ian Hickson wrote:
On Sun, 23 Oct 2011, Eric Sh. wrote:
I was trying out the HTML5 context menu in firefox and I saw that there
is no way(in the specs) to create an empty menu with only selected
context menu items in it.
So for example if I
I've just checked in a somewhat large redesign of how context menus work
in HTML. It's much more similar, though not identical, to what Firefox
implements. It drops the command element, adds a menuitem element,
introduces a button type=menu feature, and drops menu type=toolbar.
High-level
On Fri, Dec 28, 2012 at 5:23 PM, Ian Hickson i...@hixie.ch wrote:
On Sat, 22 Oct 2011, Jonas Sicking wrote:
I filed http://www.w3.org/Bugs/Public/show_bug.cgi?id=12999 on this a
while ago. So far no changes to the spec though.
I'm not sure I really agree with the premise of the bug. It
(Oops, in my earlier message I cc'ed people instead of bcc'ing them, and
this means reply-to-all replies are going to get caught in the mailing
list software's filters. If you reply to this thread, please don't forget
to strip the cc list down to nothing or only one or two people. If you
On Fri, Dec 28, 2012 at 8:45 PM, Ian Hickson i...@hixie.ch wrote:
On Fri, 28 Dec 2012, Jonas Sicking wrote:
[rearranging the thread a bit here]
While mean that authors still wouldn't have 100% control over the UX,
they would have dramatically more control than as the proposal stands
now,
On Fri, 28 Dec 2012, Jonas Sicking wrote:
I don't think it's a good solution to leave it undefined if
all/none/some of the UA menuitems are displayed by default. While it on
an API level won't break anything, authors consider as breaking a lot
more things than APIs not behaving as
18 matches
Mail list logo
