https://www.w3.org/Bugs/Public/show_bug.cgi?id=25540
Anne ann...@annevk.nl changed:
What|Removed |Added
Status|REOPENED|RESOLVED
On Mon, May 26, 2014 at 4:17 AM, Yoshifumi Inoue yo...@chromium.org wrote:
Range.style is cool idea! I assume Range.detach() removes styles added
Range.style.
detach() is a no-op. http://dom.spec.whatwg.org/#dom-range-detach
To implement text composition with this, I would like to have wave
On 26/05/2014 05:43 , Norbert Lindenberg wrote:
On May 23, 2014, at 5:19 , Robin Berjon ro...@w3.org wrote:
Which brings me to think: when we discussed this at the Summit,
there was some agreement (between all four of us :) that it was a
good idea to support multi-range selections. These are
On 26/05/2014 10:25 , Anne van Kesteren wrote:
On Mon, May 26, 2014 at 4:17 AM, Yoshifumi Inoue yo...@chromium.org wrote:
Range.style is cool idea! I assume Range.detach() removes styles added
Range.style.
detach() is a no-op. http://dom.spec.whatwg.org/#dom-range-detach
You're jumping in
Dear fellow chairs,
The CSS WG decided to issue a last call for:
Title:
CSS Font Loading Module Level 3
URL:
http://www.w3.org/TR/css-font-loading-3/
Editors' draft:
http://dev.w3.org/csswg/css-font-loading/
Abstract:
This CSS module describes
On May 23, 2014, at 5:19 , Robin Berjon ro...@w3.org wrote:
Which brings me to think: when we discussed this at the Summit, there was
some agreement (between all four of us :) that it was a good idea to support
multi-range selections. These are useful not just for tables, but also for
Since we had no topic suggestions, let's cancel the call this week.
:DG
On Fri, May 23, 2014 at 12:36 PM, Dimitri Glazkov dglaz...@google.com wrote:
As a reminder, we have our standing meeting next week:
https://www.w3.org/wiki/WebComponents/
Please reply to this mail with your agenda
Hi,
Quick update: the Editors have closed off all V1 bugs for [manifest] and
implementations in Blink and Gecko are underway. A thorough review of
[manifest] by interested parties would be greatly appreciated! You can file
bugs in our GitHub [bug tracker].
We now have the option to cherry-pick
5. There should be no native toolbars in cE=minimal (and other native UI
interfering) like the one Safari opens on iOS if you have non-empty
selection.
I haven't yet checked exactly what's in the iOS toolbar, but generally
I don't think we should dictate UI. Clearly on mobile we don't want to
-Original Message-
From: Robin Berjon [mailto:ro...@w3.org]
Sent: Monday, May 26, 2014 1:41 AM
To: Norbert Lindenberg
Cc: Jonas Sicking; Piotr Koszuliński; Ben Peters; public-webapps
Subject: Re: contentEditable=minimal
On 26/05/2014 05:43 , Norbert Lindenberg wrote:
On May 23,
-Original Message-
From: Robin Berjon [mailto:ro...@w3.org]
On 23/05/2014 01:23 , Ben Peters wrote:
As I said I am unsure that the way in which composition events are
described in DOM 3 Events is perfect, but that's only because I
haven't used them in anger and they aren't
From: Robin Berjon [mailto:ro...@w3.org]
On 23/05/2014 11:55 , Jonas Sicking wrote:
On Thu, May 22, 2014 at 3:59 AM, Piotr Koszuliński
5. Navigating with arrow keys, selection with SHIFT, CTRL modifier.
Agreed. Developers have to deal with selection moving around anyway
since they
12 matches
Mail list logo
