https://www.w3.org/Bugs/Public/show_bug.cgi?id=27552 Bug ID: 27552 Summary: Make execCommand(InsertImage, false, ) insert an img element with no src attribute Product: WebAppsWG Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P2 Component: HTML Editing APIs Assignee: a...@aryeh.name Reporter: phil...@opera.com QA Contact: sideshowbarker+html-editing-...@gmail.com CC: m...@w3.org, email@example.com The spec currently says to return false and do nothing if value is the empty string. This isn't what IE and Blink do. IE inserts an img with no src attribute and returns true. Blink inserts an img with src= and returns true. I would like to align Blink with IE's behavior, always returning false seems like a riskier change with no obvious upside. -- You are receiving this mail because: You are on the CC list for the bug.
On 11/21/14 8:43 AM, Philippe Le Hegaret wrote: On Wed, 2014-11-19 at 09:44 -0500, Arthur Barstow wrote: On 11/19/14 9:35 AM, Anne van Kesteren wrote: On Wed, Nov 19, 2014 at 3:20 PM, Arthur Barstow art.bars...@gmail.com wrote: Although there appears to be agreement that work on the [uievents] spec should stop, the various replies raise sufficient questions that I consider this CfC (as written) as failed. Travis, Gary - would you please make a specific proposal for these two specs? In particular, what is the title and shortname for each document, and which spec/shortname becomes the WG Note? After we have agreed on a way forward, I'll start a new CfC. (I believe the Principle of Least Surprise here means considering specs that currently reference [uievents] or [DOM-Level-3-Events]. F.ex., I suppose a document titled UI Events with a shortname of DOM-Level-3-Events could be a bit confusing to some, although strictly speaking could be done.) My proposal would be to update UI Events with the latest editor's draft of DOM Level 3 Events (title renamed, of course) and have the DOM Level 3 Events URL redirect to UI Events. That would communicate clearly what happened. Yves, Philippe - can Anne's proposal be done? I'm not aware of any reason that would prevent us from doing so. Hi Travis, Gary, Philippe, Since Anne's proposal hasn't been implemented, what exactly is the plan for these two specs? There is also a related proposal DOM L3 Events Input Events Work to the Editing Task Force by Ben [Ben] and followup by Gary [Gary]. What do you recommend here, i.e., Who is going to do What and When? -Thanks, ArtB [Ben] http://lists.w3.org/Archives/Public/public-webapps/2014OctDec/0575.html [Gary] http://lists.w3.org/Archives/Public/public-webapps/2014OctDec/0576.html
On Wed, 2014-12-10 at 10:22 -0500, Arthur Barstow wrote: Hi Travis, Gary, Philippe, Since Anne's proposal hasn't been implemented, what exactly is the plan for these two specs? There is also a related proposal DOM L3 Events Input Events Work to the Editing Task Force by Ben [Ben] and followup by Gary [Gary]. What do you recommend here, i.e., Who is going to do What and When? I sent a few questions to the editors on this front but didn't receive responses. I'd like some guidances here before publishing. Philippe
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27550 Morrita Hajime morr...@google.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Morrita Hajime morr...@google.com --- https://github.com/w3c/webcomponents/commit/c8f94b1819e661d7fad8309de976a766fb70fd1c -- You are receiving this mail because: You are on the CC list for the bug.
Dimitri prepared a new Working Draft of Custom Elements for publication on December 16: http://w3c.github.io/webcomponents/publish/custom/WD-custom-elements-20141218/ If anyone has any major concerns about this proposal, please speak up. -Thanks, AB