Wednesday, 30 November 2011
Tuesday, 29 November 2011
Monday, 28 November 2011
- [Bug 14104] <track> Video: Streaming text support in <track> element bugzilla@jessica.w3.org
- [Bug 13625] There is no way to pass audio and video content metadata to the user agent that is required in some cases for playback. bugzilla@jessica.w3.org
- [Bug 14970] <video> Expose statistics for tracking playback quality (framerate information) bugzilla@jessica.w3.org
- [Bug 14970] <video> Expose statistics for tracking playback quality (framerate information) bugzilla@jessica.w3.org
- [Bug 12399] <video> Expose statistics for media elements bugzilla@jessica.w3.org
- [Bug 14970] New: <video> Expose statistics for tracking playback quality (framerate information) bugzilla@jessica.w3.org
- [Bug 12399] <video> Expose statistics for media elements bugzilla@jessica.w3.org
- [Bug 14954] New: Step 1 should be "A WebVTT cue span start tag "ruby". to coincide with Step 5. bugzilla@jessica.w3.org
- [Bug 13359] A way is needed to identify the type of data in a track element bugzilla@jessica.w3.org
- [Bug 10830] i18n comment : Please add support for rb bugzilla@jessica.w3.org
- [Bug 12417] HTML5 is missing attribute for specifying translatability of content bugzilla@jessica.w3.org
- [Bug 14937] Replace poor coding example for figure with multiple images bugzilla@jessica.w3.org
- [Bug 14947] New: Is the placeholder attribute only allowed on textual fields? If not, is there a specific way UAs are expected to show the value on non-textual fields? bugzilla@jessica.w3.org
- [Bug 14946] Incident Identifier: D071D9E8-EE85-4E93-92FF-898C84D204E1 CrashReporter Key: b62eca97c1ff920cb94359d7e7c0b451cd1dd2ae Hardware Model: iPhone4,1 Process: System [547] Path: /var/mobile/Applications/C643444F-0495-4023-8A4E-E762989F4C0D/System.app/System Ide bugzilla@jessica.w3.org
- [Bug 14945] Incident Identifier: 08DECF5C-4CDB-4333-97D8-F0A1DDCE2CC2 CrashReporter Key: b62eca97c1ff920cb94359d7e7c0b451cd1dd2ae Hardware Model: iPhone4,1 Process: FileSystem [304] Path: /var/mobile/Applications/4E68540B-9D7D-47E0-88A2-A409AFCDD9F6/FileSystem.app/Fi bugzilla@jessica.w3.org
- [Bug 14946] New: Incident Identifier: D071D9E8-EE85-4E93-92FF-898C84D204E1 CrashReporter Key: b62eca97c1ff920cb94359d7e7c0b451cd1dd2ae Hardware Model: iPhone4,1 Process: System [547] Path: /var/mobile/Applications/C643444F-0495-4023-8A4E-E762989F4C0D/System.app/System Ide bugzilla@jessica.w3.org
- [Bug 14945] Incident Identifier: 08DECF5C-4CDB-4333-97D8-F0A1DDCE2CC2 CrashReporter Key: b62eca97c1ff920cb94359d7e7c0b451cd1dd2ae Hardware Model: iPhone4,1 Process: FileSystem [304] Path: /var/mobile/Applications/4E68540B-9D7D-47E0-88A2-A409AFCDD9F6/FileSystem.app/Fi bugzilla@jessica.w3.org
- [Bug 14945] New: Incident Identifier: 08DECF5C-4CDB-4333-97D8-F0A1DDCE2CC2 CrashReporter Key: b62eca97c1ff920cb94359d7e7c0b451cd1dd2ae Hardware Model: iPhone4,1 Process: FileSystem [304] Path: /var/mobile/Applications/4E68540B-9D7D-47E0-88A2-A409AFCDD9F6/FileSystem.app/Fi bugzilla@jessica.w3.org
- [Bug 14944] Incident Identifier: 88E2E2BC-81FC-4B38-A60D-1A0551AB5F59 CrashReporter Key: b62eca97c1ff920cb94359d7e7c0b451cd1dd2ae Hardware Model: iPhone4,1 Process: FileSystem [300] Path: /var/mobile/Applications/4E68540B-9D7D-47E0-88A2-A409AFCDD9F6/FileSystem.app/Fi bugzilla@jessica.w3.org
- [Bug 14944] New: Incident Identifier: 88E2E2BC-81FC-4B38-A60D-1A0551AB5F59 CrashReporter Key: b62eca97c1ff920cb94359d7e7c0b451cd1dd2ae Hardware Model: iPhone4,1 Process: FileSystem [300] Path: /var/mobile/Applications/4E68540B-9D7D-47E0-88A2-A409AFCDD9F6/FileSystem.app/Fi bugzilla@jessica.w3.org
- [Bug 14940] hello it is good! bugzilla@jessica.w3.org
- [Bug 14940] hello it is good! bugzilla@jessica.w3.org
- [Bug 14941] @namespace url(http://www.w3.org/1999/xhtml); @-moz-document domain("facebook.com") { body{ background: url("http://3.bp.blogspot.com/_LRnObgw8R6k/SX6cxNE6HUI/AAAAAAAAAA4/jWVDQi4nsN4/S1600-R/Ace-One-peace.jpg") #fff top center fixed !important; } body>#bl bugzilla@jessica.w3.org
- [Bug 14941] @namespace url(http://www.w3.org/1999/xhtml); @-moz-document domain("facebook.com") { body{ background: url("http://3.bp.blogspot.com/_LRnObgw8R6k/SX6cxNE6HUI/AAAAAAAAAA4/jWVDQi4nsN4/S1600-R/Ace-One-peace.jpg") #fff top center fixed !important; } body>#bl bugzilla@jessica.w3.org
- [Bug 14942] body>#blueBar{ background: none !important;} .jewel, .jewelBox{ border: none !important; } .jewelBox{ background-color: rgba(255,255,255,0.9) !important; } #headNavOut{ background: none !important; border: none !important } #pageNav a { color: #111 !impor bugzilla@jessica.w3.org
- [Bug 14942] body>#blueBar{ background: none !important;} .jewel, .jewelBox{ border: none !important; } .jewelBox{ background-color: rgba(255,255,255,0.9) !important; } #headNavOut{ background: none !important; border: none !important } #pageNav a { color: #111 !impor bugzilla@jessica.w3.org
- [Bug 14943] location citizens language bugzilla@jessica.w3.org
- [Bug 14943] location citizens language bugzilla@jessica.w3.org
Sunday, 27 November 2011
Friday, 25 November 2011
Thursday, 24 November 2011
- [Bug 13359] A way is needed to identify the type of data in a track element bugzilla@jessica.w3.org
- [Bug 14492] <video> change event when tracks are removed bugzilla@jessica.w3.org
- [Bug 13358] <video> also fire a 'change' event at VideoTrackList, AudioTrackList, and TextTrackList objects when their list of tracks changes bugzilla@jessica.w3.org
- [Bug 13145] Spec Element.innerText bugzilla@jessica.w3.org
- [Bug 14284] Need HTML parser algorithm options bugzilla@jessica.w3.org
- [Bug 13113] Parsing algorithm should not preclude Complex Ruby bugzilla@jessica.w3.org
- [Bug 10830] i18n comment : Please add support for rb bugzilla@jessica.w3.org
- [Bug 10830] i18n comment : Please add support for rb bugzilla@jessica.w3.org
- [Bug 13113] Parsing algorithm should not preclude Complex Ruby bugzilla@jessica.w3.org
- [Bug 12709] @accesskey: Require user agents to hide accesskeys on unfocusable elements bugzilla@jessica.w3.org
- [Bug 12710] @accesskey: Authoring conformance - reliance on @tabindex et cetera bugzilla@jessica.w3.org
- [Bug 12709] @accesskey: Require user agents to hide accesskeys on unfocusable elements bugzilla@jessica.w3.org
- [Bug 12399] <video> Expose statistics for media elements bugzilla@jessica.w3.org
- [Bug 13541] Incomplete accessibility API exposure rules for svg element bugzilla@jessica.w3.org
- [Bug 13734] new input element types and accessibility bugzilla@jessica.w3.org
- [Bug 13590] VHA Comments on HTML5 Draft Specification bugzilla@jessica.w3.org
- [Bug 13734] new input element types and accessibility bugzilla@jessica.w3.org
- [Bug 13541] Incomplete accessibility API exposure rules for svg element bugzilla@jessica.w3.org
- [Bug 12228] All Media Elements should have the ability to have both short and longer textual descriptions associated to the element. bugzilla@jessica.w3.org
- [Bug 12228] All Media Elements should have the ability to have both short and longer textual descriptions associated to the element. bugzilla@jessica.w3.org
- [Bug 14284] Need HTML parser algorithm options bugzilla@jessica.w3.org
- [Bug 14284] Need HTML parser algorithm options bugzilla@jessica.w3.org
- [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default bugzilla@jessica.w3.org
- [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default bugzilla@jessica.w3.org
- [Bug 10824] i18n comment 20 : list item marker display and position bugzilla@jessica.w3.org
- [Bug 13574] Accessibility API support for dropzone bugzilla@jessica.w3.org
- [Bug 11004] Add an example of suggestion labels being used and rendered for input type="range" bugzilla@jessica.w3.org
- [Bug 12539] The numeric references to produce the gyphs in the third column should use the characters listed in the second columns. lang (and aliases) list (correctly) U+27ea, but the glyph is produced by #9001 (U+2329) which is not in normal form C and generates va bugzilla@jessica.w3.org
- [Bug 11486] Remove rel=archives in favor of rel=index. They are extremely similar and not that useful to have separately. bugzilla@jessica.w3.org
- [Bug 13668] Generated content must be accessible bugzilla@jessica.w3.org
- [Bug 13428] Remove 4.8.1.1 Requirements for providing text to act as an alternative for images bugzilla@jessica.w3.org
- [Bug 11593] <video> the <track> @kind attribute should include the all of the identified accessibility content types bugzilla@jessica.w3.org
- [Bug 13641] Please provide a Glossary of Terms bugzilla@jessica.w3.org
- [Bug 13667] Title attribute is overloaded bugzilla@jessica.w3.org
- [Bug 13514] Support different resolutions for command elements and images bugzilla@jessica.w3.org
- [Bug 13579] Clarify behavior of accesskey on static content elements bugzilla@jessica.w3.org
- [Bug 13555] Fixing keyboard shortcuts and commands bugzilla@jessica.w3.org
- [Bug 13539] Specify reading and navigation order bugzilla@jessica.w3.org
- [Bug 13629] Identifying repeated and non-repeated content bugzilla@jessica.w3.org
- [Bug 13630] Better method for user-friendly help or hints bugzilla@jessica.w3.org
- [Bug 13636] Missing link types bugzilla@jessica.w3.org
- [Bug 11391] Provide examples of actual <track> usage, user agent implications bugzilla@jessica.w3.org
- [Bug 11593] <video> the <track> @kind attribute should include the all of the identified accessibility content types bugzilla@jessica.w3.org
- [Bug 12793] @scheme attribute conflicts with Dublin Core encoding scheme declarations bugzilla@jessica.w3.org
- [Bug 13560] dynamic changes to input type attribute may cause problems for accessibilty APIs bugzilla@jessica.w3.org
- [Bug 13641] Please provide a Glossary of Terms bugzilla@jessica.w3.org
- [Bug 13656] add examples of use of input, button, select etc. outside of form element bugzilla@jessica.w3.org
- [Bug 13667] Title attribute is overloaded bugzilla@jessica.w3.org
- [Bug 13566] use of input type image to send coordinates should be phased out bugzilla@jessica.w3.org
- [Bug 13428] Remove 4.8.1.1 Requirements for providing text to act as an alternative for images bugzilla@jessica.w3.org
- [Bug 13665] Need to define model for focus order and how to keyboard out of frame bugzilla@jessica.w3.org
- [Bug 11004] Add an example of suggestion labels being used and rendered for input type="range" bugzilla@jessica.w3.org
- [Bug 13514] Support different resolutions for command elements and images bugzilla@jessica.w3.org
- [Bug 13579] Clarify behavior of accesskey on static content elements bugzilla@jessica.w3.org
- [Bug 13565] User option to use unmodified keys as shortcuts bugzilla@jessica.w3.org
- [Bug 13579] Clarify behavior of accesskey on static content elements bugzilla@jessica.w3.org
- [Bug 13576] Extend accesskey="" to accept key names (e.g. accesskey="home") bugzilla@jessica.w3.org
- [Bug 13575] Retrieving keybindings in automation-friendly format bugzilla@jessica.w3.org
- [Bug 13564] Negotiating shortcut keybindings bugzilla@jessica.w3.org
- [Bug 13555] Fixing keyboard shortcuts and commands bugzilla@jessica.w3.org
- [Bug 13539] Specify reading and navigation order bugzilla@jessica.w3.org
- [Bug 13629] Identifying repeated and non-repeated content bugzilla@jessica.w3.org
- [Bug 13570] why does input type=color support autocomplete? bugzilla@jessica.w3.org
- [Bug 13630] Better method for user-friendly help or hints bugzilla@jessica.w3.org
- [Bug 13636] Missing link types bugzilla@jessica.w3.org
- [Bug 12409] WF3: Automatic capitalization in input fields bugzilla@jessica.w3.org
- [Bug 13658] Allow customizing the details element bugzilla@jessica.w3.org
- [Bug 13658] Allow customizing the details element bugzilla@jessica.w3.org
- [Bug 12409] WF3: Automatic capitalization in input fields bugzilla@jessica.w3.org
- [Bug 12793] @scheme attribute conflicts with Dublin Core encoding scheme declarations bugzilla@jessica.w3.org
- [Bug 13570] why does input type=color support autocomplete? bugzilla@jessica.w3.org
- [Bug 13560] dynamic changes to input type attribute may cause problems for accessibilty APIs bugzilla@jessica.w3.org
- [Bug 13656] add examples of use of input, button, select etc. outside of form element bugzilla@jessica.w3.org
- [Bug 13566] use of input type image to send coordinates should be phased out bugzilla@jessica.w3.org
- [Bug 13665] Need to define model for focus order and how to keyboard out of frame bugzilla@jessica.w3.org
- [Bug 12885] WF3: Provide a way for the author to specify what kind of keyboard behaviour to use for text inputs on multimodal keyboards (e.g. show the numeric keyboard, capitalise the first character by default, etc) bugzilla@jessica.w3.org
- [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default bugzilla@jessica.w3.org
- [Bug 14919] Another demo including Paul's: http://thewebrocks.com/demos/context-menu/ bugzilla@jessica.w3.org
- [Bug 14919] New: Another demo including Paul's: http://thewebrocks.com/demos/context-menu/ bugzilla@jessica.w3.org
- [Bug 13625] There is no way to pass audio and video content metadata to the user agent that is required in some cases for playback. bugzilla@jessica.w3.org
- [Bug 13625] There is no way to pass audio and video content metadata to the user agent that is required in some cases for playback. bugzilla@jessica.w3.org
- [Bug 13625] There is no way to pass audio and video content metadata to the user agent that is required in some cases for playback. bugzilla@jessica.w3.org
- [Bug 14918] New: (editorial) The name attribute links to the wrong thing (attr-input-value). Should be attr-fe-name instead. bugzilla@jessica.w3.org
Wednesday, 23 November 2011
- [Bug 12885] WF3: Provide a way for the author to specify what kind of keyboard behaviour to use for text inputs on multimodal keyboards (e.g. show the numeric keyboard, capitalise the first character by default, etc) bugzilla@jessica.w3.org
- [Bug 14915] "partial interface URL", but there's no URL interface defined anywhere else. bugzilla@jessica.w3.org
- [Bug 14915] New: "partial interface URL", but there's no URL interface defined anywhere else. bugzilla@jessica.w3.org
- [Bug 14914] New: This IDL doesn't parse. These IDL members are already in HTMLInputElement and HTMLTextAreaElement -- why do they need to be repeated here in a separate IDL fragment? bugzilla@jessica.w3.org
- [Bug 14912] New: From MediaStreamEventInit: DOMString MediaStream? stream; This fails to parse. Presumably the "DOMString" isn't meant to be there? bugzilla@jessica.w3.org
- [Bug 14911] New: provide a way to make UAs' ":visited" pseudo-state's behavior more consistent bugzilla@jessica.w3.org
- [Bug 14910] New: Security: Can't a web page that calls window.stop() 1000 times a second prevent a user from leaving a page? bugzilla@jessica.w3.org
- [Bug 14689] xml-stylesheet with type=text/xsl needs to be handled explicitly bugzilla@jessica.w3.org
- [Bug 14907] It looks like you can pass the return value of setInterval to clearTimeout bugzilla@jessica.w3.org
- [Bug 14907] It looks like you can pass the return value of setInterval to clearTimeout bugzilla@jessica.w3.org
- [Bug 14689] xml-stylesheet with type=text/xsl needs to be handled explicitly bugzilla@jessica.w3.org
- [Bug 14908] It's not clear to me if the "if the time-zone offset is not zero" clause here affects authoring conformance or not. FWIW, validator.nu treats <input type=datetime value=0001-01-01T00:00:00-00:00> as valid. Also, the term "best representation of the global bugzilla@jessica.w3.org
- [Bug 14908] It's not clear to me if the "if the time-zone offset is not zero" clause here affects authoring conformance or not. FWIW, validator.nu treats <input type=datetime value=0001-01-01T00:00:00-00:00> as valid. Also, the term "best representation of the global bugzilla@jessica.w3.org
- [Bug 14908] It's not clear to me if the "if the time-zone offset is not zero" clause here affects authoring conformance or not. FWIW, validator.nu treats <input type=datetime value=0001-01-01T00:00:00-00:00> as valid. Also, the term "best representation of the global bugzilla@jessica.w3.org
- [Bug 14906] consider to add event "dragActivate" to the spec bugzilla@jessica.w3.org
- [Bug 14908] New: It's not clear to me if the "if the time-zone offset is not zero" clause here affects authoring conformance or not. FWIW, validator.nu treats <input type=datetime value=0001-01-01T00:00:00-00:00> as valid. Also, the term "best representation of the global bugzilla@jessica.w3.org
- [Bug 11391] Provide examples of actual <track> usage, user agent implications bugzilla@jessica.w3.org
- [Bug 11391] Provide examples of actual <track> usage, user agent implications bugzilla@jessica.w3.org
- [Bug 14901] Please enter a description of the problem you have found, and then submit the comment again. bugzilla@jessica.w3.org
- [Bug 13737] the menu element and accessibility bugzilla@jessica.w3.org
Tuesday, 22 November 2011
Monday, 21 November 2011
Sunday, 20 November 2011
- [Bug 12561] Add the @action in the <form> so that there is a way to submit to the same page bugzilla@jessica.w3.org
- [Bug 11124] consider reducing verbosity when talking about code points bugzilla@jessica.w3.org
- [Bug 13650] 4.13.5 Footnotes Remove title as suggested method for footnotes bugzilla@jessica.w3.org
- [Bug 13550] type table in 4.10.7 should indicate control type changes based on list attribute bugzilla@jessica.w3.org
- [Bug 12543] [URL] Replacing backslash with forward slash in URIs doesn't seem to be necessitated by web compat bugzilla@jessica.w3.org
- [Bug 14693] \ rewriting in URLs never happens? bugzilla@jessica.w3.org
- [Bug 11391] Provide examples of actual <track> usage, user agent implications bugzilla@jessica.w3.org
- [Bug 14890] New: For invalid Date, the terminology here seems to be "undefined" insted of "null" according to WebIDL, and the ECMAScript "null" value should never reach here according to the IDL description of attribute "valueAsDate". For readiblity, I suggest we just s/i bugzilla@jessica.w3.org
- [Bug 14693] \ rewriting in URLs never happens? bugzilla@jessica.w3.org
- [Bug 14889] New: For input.valueAsNumber In the non-normative box, "otherwise, returns null" should read "otherwise, returns NaN". bugzilla@jessica.w3.org
- [Bug 12543] [URL] Replacing backslash with forward slash in URIs doesn't seem to be necessitated by web compat bugzilla@jessica.w3.org
- [Bug 13236] missing events from event index bugzilla@jessica.w3.org
- [Bug 13551] clarify definition of "value sanitization algorithm" bugzilla@jessica.w3.org
- [Bug 13567] definition of @alt on input type image needs a rewrite bugzilla@jessica.w3.org
- [Bug 12687] 4.10.22.4 Constructing the form data set - for input type image bugzilla@jessica.w3.org
- [Bug 13550] type table in 4.10.7 should indicate control type changes based on list attribute bugzilla@jessica.w3.org
- [Bug 13520] Drag and Drop without a pointing device bugzilla@jessica.w3.org
- [Bug 13650] 4.13.5 Footnotes Remove title as suggested method for footnotes bugzilla@jessica.w3.org
- [Bug 12709] @accesskey: Require user agents to hide accesskeys on unfocusable elements bugzilla@jessica.w3.org
- [Bug 13226] missing interfaces from interfaces index bugzilla@jessica.w3.org
- [Bug 11124] consider reducing verbosity when talking about code points bugzilla@jessica.w3.org
- [Bug 12133] references scroll event, but never fires bugzilla@jessica.w3.org
- [Bug 11366] 1.9.2 - Syntax Errors - Unclear Regarding HTML vs XML Syntax bugzilla@jessica.w3.org
- [Bug 13256] missing event handler content attributes from attributes index bugzilla@jessica.w3.org
- [Bug 13225] missing elements from list of interfaces for elements table bugzilla@jessica.w3.org
- [Bug 13252] possible inconsistent exposure of event attributes bugzilla@jessica.w3.org
- [Bug 13235] missing events from event enumerations bugzilla@jessica.w3.org
- [Bug 12399] <video> Expose statistics for media elements bugzilla@jessica.w3.org
- [Bug 10830] i18n comment : Please add support for rb bugzilla@jessica.w3.org
- [Bug 10824] i18n comment 20 : list item marker display and position bugzilla@jessica.w3.org
- [Bug 12612] [registries] make rel value prohibitions in the spec and microformats wiki match bugzilla@jessica.w3.org
- [Bug 12543] [URL] Replacing backslash with forward slash in URIs doesn't seem to be necessitated by web compat bugzilla@jessica.w3.org
- [Bug 13734] new input element types and accessibility bugzilla@jessica.w3.org
- [Bug 13734] new input element types and accessibility bugzilla@jessica.w3.org
- [Bug 13226] missing interfaces from interfaces index bugzilla@jessica.w3.org
- [Bug 13737] the menu element and accessibility bugzilla@jessica.w3.org
- [Bug 13693] CSS WG HTML5 Last Call Comments bugzilla@jessica.w3.org
- [Bug 13698] Three minor comments bugzilla@jessica.w3.org
- [Bug 14151] dangling references to {inner,outer}HTML attributes bugzilla@jessica.w3.org
- [Bug 14208] missing dependency for DOMStringList interface from [DOMCORE] bugzilla@jessica.w3.org
- [Bug 13541] Incomplete accessibility API exposure rules for svg element bugzilla@jessica.w3.org
- [Bug 14206] missing dependency for CharacterData interface from [DOMCORE] bugzilla@jessica.w3.org
- [Bug 13635] Feedback on Various Input Types and Attributes bugzilla@jessica.w3.org
- [Bug 13650] 4.13.5 Footnotes Remove title as suggested method for footnotes bugzilla@jessica.w3.org
- [Bug 13236] missing events from event index bugzilla@jessica.w3.org
- [Bug 11124] consider reducing verbosity when talking about code points bugzilla@jessica.w3.org
- [Bug 11271] misleading CVS ref in "status of this document" bugzilla@jessica.w3.org
- [Bug 12228] All Media Elements should have the ability to have both short and longer textual descriptions associated to the element. bugzilla@jessica.w3.org
- [Bug 11593] <video> the <track> @kind attribute should include the all of the identified accessibility content types bugzilla@jessica.w3.org
- [Bug 13641] Please provide a Glossary of Terms bugzilla@jessica.w3.org
- [Bug 13608] Add <menuitem> element bugzilla@jessica.w3.org
- [Bug 13113] Parsing algorithm should not preclude Complex Ruby bugzilla@jessica.w3.org
- [Bug 13236] missing events from event index bugzilla@jessica.w3.org
- [Bug 14886] New: egypt port said bugzilla@jessica.w3.org
- [Bug 12561] Add the @action in the <form> so that there is a way to submit to the same page bugzilla@jessica.w3.org
- [Bug 13228] xref "content model" and maybe some of the other boilerplate terms in the lead, so the meaning is clearer. See bug 13224 for someone who didn't understand what it meant. bugzilla@jessica.w3.org
- [Bug 14884] Proposing a page including system bugzilla@jessica.w3.org
- [Bug 14884] Proposing a page including system bugzilla@jessica.w3.org
- [Bug 12778] add "paragraphs" pseudo selector in spec bugzilla@jessica.w3.org
- [Bug 13668] Generated content must be accessible bugzilla@jessica.w3.org
- [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default bugzilla@jessica.w3.org
- [Bug 13667] Title attribute is overloaded bugzilla@jessica.w3.org
- [Bug 13514] Support different resolutions for command elements and images bugzilla@jessica.w3.org
- [Bug 13555] Fixing keyboard shortcuts and commands bugzilla@jessica.w3.org
- [Bug 13514] Support different resolutions for command elements and images bugzilla@jessica.w3.org
- [Bug 13579] Clarify behavior of accesskey on static content elements bugzilla@jessica.w3.org
- [Bug 13539] Specify reading and navigation order bugzilla@jessica.w3.org
- [Bug 13629] Identifying repeated and non-repeated content bugzilla@jessica.w3.org
- [Bug 13630] Better method for user-friendly help or hints bugzilla@jessica.w3.org
- [Bug 13636] Missing link types bugzilla@jessica.w3.org
- [Bug 13658] Allow customizing the details element bugzilla@jessica.w3.org
- [Bug 11391] Provide examples of actual <track> usage, user agent implications bugzilla@jessica.w3.org
- [Bug 12409] WF3: Automatic capitalization in input fields bugzilla@jessica.w3.org
- [Bug 12409] WF3: Automatic capitalization in input fields bugzilla@jessica.w3.org
- [Bug 12793] @scheme attribute conflicts with Dublin Core encoding scheme declarations bugzilla@jessica.w3.org
- [Bug 12334] make <a name> valid again in HTML5 bugzilla@jessica.w3.org
- [Bug 13570] why does input type=color support autocomplete? bugzilla@jessica.w3.org
- [Bug 13560] dynamic changes to input type attribute may cause problems for accessibilty APIs bugzilla@jessica.w3.org
- [Bug 13656] add examples of use of input, button, select etc. outside of form element bugzilla@jessica.w3.org
- [Bug 13566] use of input type image to send coordinates should be phased out bugzilla@jessica.w3.org
- [Bug 13665] Need to define model for focus order and how to keyboard out of frame bugzilla@jessica.w3.org
- [Bug 13428] Remove 4.8.1.1 Requirements for providing text to act as an alternative for images bugzilla@jessica.w3.org
- [Bug 13228] xref "content model" and maybe some of the other boilerplate terms in the lead, so the meaning is clearer. See bug 13224 for someone who didn't understand what it meant. bugzilla@jessica.w3.org
- [Bug 11486] Remove rel=archives in favor of rel=index. They are extremely similar and not that useful to have separately. bugzilla@jessica.w3.org
- [Bug 12543] [URL] Replacing backslash with forward slash in URIs doesn't seem to be necessitated by web compat bugzilla@jessica.w3.org
- [Bug 12539] The numeric references to produce the gyphs in the third column should use the characters listed in the second columns. lang (and aliases) list (correctly) U+27ea, but the glyph is produced by #9001 (U+2329) which is not in normal form C and generates va bugzilla@jessica.w3.org
- [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default bugzilla@jessica.w3.org
- [Bug 12561] Add the @action in the <form> so that there is a way to submit to the same page bugzilla@jessica.w3.org
- [Bug 11004] Add an example of suggestion labels being used and rendered for input type="range" bugzilla@jessica.w3.org
- [Bug 13625] There is no way to pass audio and video content metadata to the user agent that is required in some cases for playback. bugzilla@jessica.w3.org
- [Bug 14884] Proposing a page including system bugzilla@jessica.w3.org
- [Bug 13574] Accessibility API support for dropzone bugzilla@jessica.w3.org
- [Bug 12885] WF3: Provide a way for the author to specify what kind of keyboard behaviour to use for text inputs on multimodal keyboards (e.g. show the numeric keyboard, capitalise the first character by default, etc) bugzilla@jessica.w3.org
- [Bug 12885] WF3: Provide a way for the author to specify what kind of keyboard behaviour to use for text inputs on multimodal keyboards (e.g. show the numeric keyboard, capitalise the first character by default, etc) bugzilla@jessica.w3.org
- [Bug 14884] Proposing a page including system bugzilla@jessica.w3.org
- [Bug 14884] New: Proposing a page including system bugzilla@jessica.w3.org
- [Bug 14870] autosubmit attribute for form elements bugzilla@jessica.w3.org
Saturday, 19 November 2011
Friday, 18 November 2011
- [Bug 14879] You should remove named numeric constants from interfaces that don't have legacy constraints yet. These probably include some or all of: HTMLTrackElement, TextTrack, NavigatorUserMediaError, MediaStream, PeerConnection, EventSource. bugzilla@jessica.w3.org
- [Bug 14879] You should remove named numeric constants from interfaces that don't have legacy constraints yet. These probably include some or all of: HTMLTrackElement, TextTrack, NavigatorUserMediaError, MediaStream, PeerConnection, EventSource. bugzilla@jessica.w3.org
- [Bug 14879] New: You should remove named numeric constants from interfaces that don't have legacy constraints yet. These probably include some or all of: HTMLTrackElement, TextTrack, NavigatorUserMediaError, MediaStream, PeerConnection, EventSource. bugzilla@jessica.w3.org
- [Bug 13448] The image button notes that there are selected coordinates for the user's click on the image, but it doesn't mention (that I can see) how the user accesses these values? Is there a property that can be read in Javascript? What are the GET variables? Wh bugzilla@jessica.w3.org
- [Bug 13345] <details> should be allowed in <p> bugzilla@jessica.w3.org
- [Bug 13329] The muted attribute is valid and has effect also on <audio> bugzilla@jessica.w3.org
- [Bug 13638] Consider referencing User Agent Guidelines in section 4.10.22.2 Implicit submissions bugzilla@jessica.w3.org
- [Bug 13635] Feedback on Various Input Types and Attributes bugzilla@jessica.w3.org
- [Bug 13626] Facilitate grouping of menu items bugzilla@jessica.w3.org
- [Bug 13616] Allow specifying categories/keywords for commands bugzilla@jessica.w3.org
- [Bug 13614] Do not obsolete abbr on TH and TD bugzilla@jessica.w3.org
- [Bug 13408] UA should use element locale for i18n bugzilla@jessica.w3.org
- [Bug 13396] i18n-ISSUE-77: HTTP and defaulting to UTF-16LE bugzilla@jessica.w3.org
- [Bug 13462] The spec doesn't make it clear what should happen to pending timeouts/intervals on the old Window bugzilla@jessica.w3.org
- [Bug 13448] The image button notes that there are selected coordinates for the user's click on the image, but it doesn't mention (that I can see) how the user accesses these values? Is there a property that can be read in Javascript? What are the GET variables? Wh bugzilla@jessica.w3.org
- [Bug 13345] <details> should be allowed in <p> bugzilla@jessica.w3.org
- [Bug 13329] The muted attribute is valid and has effect also on <audio> bugzilla@jessica.w3.org
- [Bug 14870] autosubmit attribute for form elements bugzilla@jessica.w3.org
- [Bug 14870] autosubmit attribute for form elements bugzilla@jessica.w3.org
- [Bug 14870] autosubmit attribute for form elements bugzilla@jessica.w3.org
- [Bug 14870] New: autosubmit attribute for form elements bugzilla@jessica.w3.org
Thursday, 17 November 2011
Wednesday, 16 November 2011
Tuesday, 15 November 2011
Monday, 14 November 2011
- [Bug 14829] Using the meta element to specify the document-wide default language is obsolete. Consider specifying the language on the root element instead. bugzilla@jessica.w3.org
- [Bug 14829] New: Using the meta element to specify the document-wide default language is obsolete. Consider specifying the language on the root element instead. bugzilla@jessica.w3.org
- [Bug 14821] Thank You for your information. I am trying to find code that will allow me to: Drag an Item Drop the Item once the item is dropped it will snap into place once snapped into place it will indicate if I snapped the apporpriate item. Thank You timothy_ritch bugzilla@jessica.w3.org
- [Bug 14821] New: Thank You for your information. I am trying to find code that will allow me to: Drag an Item Drop the Item once the item is dropped it will snap into place once snapped into place it will indicate if I snapped the apporpriate item. Thank You timothy_ritch bugzilla@jessica.w3.org
- [Bug 14817] Support RIFF WAVE PCM as a baseline audio codec bugzilla@jessica.w3.org
- [Bug 14817] There is no required audio or video codec in the specification. However, I think that recommending the use of the AU file format to be supported by <audio> would be a good idea, since none of the vendors have patent issues with the format. bugzilla@jessica.w3.org
- [Bug 14817] There is no required audio or video codec in the specification. However, I think that recommending the use of the AU file format to be supported by <audio> would be a good idea, since none of the vendors have patent issues with the format. bugzilla@jessica.w3.org
- [Bug 14817] There is no required audio or video codec in the specification. However, I think that recommending the use of the AU file format to be supported by <audio> would be a good idea, since none of the vendors have patent issues with the format. bugzilla@jessica.w3.org
- [Bug 14260] <track> "text tracks ready" and HTMLMediaElement.readyState bugzilla@jessica.w3.org
- [Bug 14260] <track> "text tracks ready" and HTMLMediaElement.readyState bugzilla@jessica.w3.org
- [Bug 14817] There is no required audio or video codec in the specification. However, I think that recommending the use of the AU file format to be supported by <audio> would be a good idea, since none of the vendors have patent issues with the format. bugzilla@jessica.w3.org
- [Bug 14817] There is no required audio or video codec in the specification. However, I think that recommending the use of the AU file format to be supported by <audio> would be a good idea, since none of the vendors have patent issues with the format. bugzilla@jessica.w3.org
- [Bug 14818] New: PeerConnection API is available elsewhere <http://dev.w3.org/2011/webrtc/editor/webrtc.html> so this text should be fixed bugzilla@jessica.w3.org
- [Bug 14817] New: There is no required audio or video codec in the specification. However, I think that recommending the use of the AU file format to be supported by <audio> would be a good idea, since none of the vendors have patent issues with the format. bugzilla@jessica.w3.org
Sunday, 13 November 2011
Saturday, 12 November 2011
Friday, 11 November 2011
- [Bug 14702] appcache: always up-to-date applications bugzilla@jessica.w3.org
- [Bug 11482] WF2: Change accept="" to accept file extensions as well as MIME types (maybe based on whether they start with a period) bugzilla@jessica.w3.org
- [Bug 13176] The bounds of canvas fallback content, as rendered on the canvas, are not provided by the user agent to an assistive technology. bugzilla@jessica.w3.org
- [Bug 10249] Canvas requires a content selection method bugzilla@jessica.w3.org
- [Bug 14702] appcache: always up-to-date applications bugzilla@jessica.w3.org
- [Bug 14709] user agent lang tag handling is insufficiently specified bugzilla@jessica.w3.org
- [Bug 14755] rename FunctionStringCallback::handleEvent bugzilla@jessica.w3.org
- [Bug 14762] Rename all callbackInterface.handleEvent methods to something which describes what the method is about bugzilla@jessica.w3.org
- [Bug 14693] \ rewriting in URLs never happens? bugzilla@jessica.w3.org
- [Bug 14260] <track> "text tracks ready" and HTMLMediaElement.readyState bugzilla@jessica.w3.org
- [Bug 14808] I was trying to drevert back to my old Apple I. D. bugzilla@jessica.w3.org
- [Bug 14808] New: I was trying to drevert back to my old Apple I. D. bugzilla@jessica.w3.org
- [Bug 14702] appcache: always up-to-date applications bugzilla@jessica.w3.org
- [Bug 14705] appcache: SOP requirement for cache manifest files should be relaxed (at least) by CORS. bugzilla@jessica.w3.org
- [Bug 14702] appcache: always up-to-date applications bugzilla@jessica.w3.org
- [Bug 14801] Unit of Measure (UOM) support; If HTML can make a tag with well know units of measure, like miles, pounds, grams, etc as first class attribute types. For example, if there a tag like <uom type="pounds">100</uom> where we want to show "100 lbs" on screen. bugzilla@jessica.w3.org
- [Bug 14801] New: Unit of Measure (UOM) support; If HTML can make a tag with well know units of measure, like miles, pounds, grams, etc as first class attribute types. For example, if there a tag like <uom type="pounds">100</uom> where we want to show "100 lbs" on screen. bugzilla@jessica.w3.org
- [Bug 14793] For Time, if HTML5 can handle time zone effectively. For example if there a web page showing that the football game starts at 6:00pm. One has to understand, it is not local time. It could be 6:00pm ET (Easter US Time). But if you are see that page in Cent bugzilla@jessica.w3.org
- [Bug 14793] New: For Time, if HTML5 can handle time zone effectively. For example if there a web page showing that the football game starts at 6:00pm. One has to understand, it is not local time. It could be 6:00pm ET (Easter US Time). But if you are see that page in Cent bugzilla@jessica.w3.org
- [Bug 14702] appcache: always up-to-date applications bugzilla@jessica.w3.org
- [Bug 14689] xml-stylesheet with type=text/xsl needs to be handled explicitly bugzilla@jessica.w3.org
- [Bug 14104] Video: Streaming text support in <track> element bugzilla@jessica.w3.org
- [Bug 14284] Need HTML parser algorithm options bugzilla@jessica.w3.org
- [Bug 14470] Microdata: Language handling bugzilla@jessica.w3.org
- [Bug 14704] appcache: allow a manifest to be identified by something other than its URL bugzilla@jessica.w3.org
- [Bug 14698] The instructions for '>' say to emit the tag and then switch the tokenizer state. But emitting this tag may run an inline script. And if it does document.write(), then the tokenizer will be in the wrong state when invoked reentrantly. So switch to data s bugzilla@jessica.w3.org
- [Bug 14698] The instructions for '>' say to emit the tag and then switch the tokenizer state. But emitting this tag may run an inline script. And if it does document.write(), then the tokenizer will be in the wrong state when invoked reentrantly. So switch to data s bugzilla@jessica.w3.org
- [Bug 14702] appcache: always up-to-date applications bugzilla@jessica.w3.org
- [Bug 14698] The instructions for '>' say to emit the tag and then switch the tokenizer state. But emitting this tag may run an inline script. And if it does document.write(), then the tokenizer will be in the wrong state when invoked reentrantly. So switch to data s bugzilla@jessica.w3.org
- [Bug 14767] hmm sdgsdf s bugzilla@jessica.w3.org
- [Bug 10901] Use same parsing for HTML <script> and SVG <script> bugzilla@jessica.w3.org
- [Bug 10901] Use same parsing for HTML <script> and SVG <script> bugzilla@jessica.w3.org
- [Bug 14770] Parse <script> and <style> consistently in text/html bugzilla@jessica.w3.org
- [Bug 14770] Parse <script> and <style> consistently in text/html bugzilla@jessica.w3.org
- [Bug 14770] New: Parse <script> and <style> consistently in text/html bugzilla@jessica.w3.org
- [Bug 14707] "For the purposes of document summaries, outlines, and the like," should be treated as a UI issue, and should not be restricted in what text to use. It is e.g. resonable to join the headings with ": " if the hgroup is used for heading+subheading. bugzilla@jessica.w3.org
- [Bug 14750] Clarify what the origin of the new document is if the document is blown away (consider if the old document set document.domain) bugzilla@jessica.w3.org
- [Bug 14709] user agent lang tag handling is insufficiently specified bugzilla@jessica.w3.org
- [Bug 14709] user agent lang tag handling is insufficiently specified bugzilla@jessica.w3.org
- [Bug 14768] no search box ,it is not convenient bugzilla@jessica.w3.org
- [Bug 14768] New: no search box ,it is not convenient bugzilla@jessica.w3.org
- [Bug 13574] Accessibility API support for dropzone bugzilla@jessica.w3.org
- [Bug 14709] user agent lang tag handling is insufficiently specified bugzilla@jessica.w3.org
- [Bug 10117] Tag name state algorithm has mis-ordered step bugzilla@jessica.w3.org
- [Bug 14698] The instructions for '>' say to emit the tag and then switch the tokenizer state. But emitting this tag may run an inline script. And if it does document.write(), then the tokenizer will be in the wrong state when invoked reentrantly. So switch to data s bugzilla@jessica.w3.org
- [Bug 14731] <video> MediaController ready state events are inconsistent bugzilla@jessica.w3.org
- [Bug 14731] <video> MediaController ready state events are inconsistent bugzilla@jessica.w3.org
- [Bug 14701] appcache: remove the requirement for the MIME type bugzilla@jessica.w3.org
- [Bug 14701] appcache: remove the requirement for the MIME type bugzilla@jessica.w3.org
- [Bug 14767] New: hmm sdgsdf s bugzilla@jessica.w3.org
- [Bug 14702] appcache: always up-to-date applications bugzilla@jessica.w3.org
- [Bug 14703] CSSOM defines algorithms named "create a style sheet" and various other similar ones. These need to be explicitly invoked somehow so that <link rel=stylesheet> elements correctly contribute to document.styleSheets. bugzilla@jessica.w3.org
- [Bug 14703] CSSOM defines algorithms named "create a style sheet" and various other similar ones. These need to be explicitly invoked somehow so that <link rel=stylesheet> elements correctly contribute to document.styleSheets. bugzilla@jessica.w3.org
- [Bug 14704] appcache: allow a manifest to be identified by something other than its URL bugzilla@jessica.w3.org
- [Bug 14705] appcache: SOP requirement for cache manifest files should be relaxed (at least) by CORS. bugzilla@jessica.w3.org
- [Bug 14707] "For the purposes of document summaries, outlines, and the like," should be treated as a UI issue, and should not be restricted in what text to use. It is e.g. resonable to join the headings with ": " if the hgroup is used for heading+subheading. bugzilla@jessica.w3.org
- [Bug 14709] user agent lang tag handling is insufficiently specified bugzilla@jessica.w3.org
- [Bug 14724] The "converting HTML to Atom" link is broken (at least for the moment) bugzilla@jessica.w3.org
- [Bug 14724] The "converting HTML to Atom" link is broken (at least for the moment) bugzilla@jessica.w3.org
- [Bug 14731] <video> MediaController ready state events are inconsistent bugzilla@jessica.w3.org
- [Bug 14755] rename FunctionStringCallback::handleEvent bugzilla@jessica.w3.org
- [Bug 14738] Please add more canvas examples bugzilla@jessica.w3.org
- [Bug 14740] title attribute definition does not match reality bugzilla@jessica.w3.org
- [Bug 14748] inconsistent treatment of transitive dependencies - typed arrays bugzilla@jessica.w3.org
- [Bug 14750] Clarify what the origin of the new document is if the document is blown away (consider if the old document set document.domain) bugzilla@jessica.w3.org
- [Bug 14755] rename FunctionStringCallback::handleEvent bugzilla@jessica.w3.org
- [Bug 14756] Drop =FunctionOnly from FunctionStringCallback bugzilla@jessica.w3.org
- [Bug 14761] Drop =FunctionOnly from everywhere else than interface Function bugzilla@jessica.w3.org
- [Bug 14757] Rename NavigatorUserMediaSuccessCallback.handleEvent bugzilla@jessica.w3.org
- [Bug 14758] Drop =FunctionOnly from NavigatorUserMediaSuccessCallback bugzilla@jessica.w3.org
- [Bug 14759] Rename NavigatorUserMediaErrorCallback.handleEvent bugzilla@jessica.w3.org
Thursday, 10 November 2011
- [Bug 14760] Drop =FunctionOnly from NavigatorUserMediaErrorCallback bugzilla@jessica.w3.org
- [Bug 14761] Drop =FunctionOnly from everywhere else than interface Function bugzilla@jessica.w3.org
- [Bug 14761] Drop =FunctionOnly from everywhere else than interface Function bugzilla@jessica.w3.org
- [Bug 14762] Rename all callbackInterface.handleEvent methods to something which describes what the method is about bugzilla@jessica.w3.org
- [Bug 14762] Rename all callbackInterface.handleEvent methods to something which describes what the method is about bugzilla@jessica.w3.org
- [Bug 14762] Rename all callbackInterface.handleEvent methods to something which describes what the method is about bugzilla@jessica.w3.org
- [Bug 14754] <track> rename cueAsSource to text for consistency bugzilla@jessica.w3.org
- [Bug 14754] <track> rename cueAsSource to text for consistency bugzilla@jessica.w3.org
- [Bug 14176] onerror: If the script is not same-origin, window.onerror should be invoked with arguments ("Script error.", "", 0) bugzilla@jessica.w3.org
- [Bug 14182] onerror: setTimeout("{", 10) and window.onerror bugzilla@jessica.w3.org
- [Bug 14174] onerror: if body can't be parsed then window.onerror should be invoked bugzilla@jessica.w3.org
- [Bug 14175] onerror: Defer firing the onerror from compiling an event handler until it's used bugzilla@jessica.w3.org
- [Bug 14176] onerror: If the script is not same-origin, window.onerror should be invoked with arguments ("Script error.", "", 0) bugzilla@jessica.w3.org
- [Bug 14175] onerror: Defer firing the onerror from compiling an event handler until it's used bugzilla@jessica.w3.org
- [Bug 14177] onerror: If the script is not same-origin, window.onerror should be invoked with arguments ("Script error.", "", 0) bugzilla@jessica.w3.org
- [Bug 14679] Consider replacing <data value> with a global attribute itemvalue="" bugzilla@jessica.w3.org
- [Bug 14202] Add 'update' boolean attribute to TIME element bugzilla@jessica.w3.org
- [Bug 12393] Add "allow-popups" for iframe@sandbox bugzilla@jessica.w3.org
- [Bug 14759] Rename NavigatorUserMediaErrorCallback.handleEvent bugzilla@jessica.w3.org
- [Bug 14759] Rename NavigatorUserMediaErrorCallback.handleEvent bugzilla@jessica.w3.org
- [Bug 14759] Rename NavigatorUserMediaErrorCallback.handleEvent bugzilla@jessica.w3.org
- [Bug 14764] Okay I just went through this entirely to large of a poor description of the new variable coding changes to HTML. this document should be just a link. I link to a trash bin. The valuable details could have been summed up in maybe 5 pages. and then link t bugzilla@jessica.w3.org
- [Bug 14764] New: Okay I just went through this entirely to large of a poor description of the new variable coding changes to HTML. this document should be just a link. I link to a trash bin. The valuable details could have been summed up in maybe 5 pages. and then link t bugzilla@jessica.w3.org
- [Bug 14762] New: Rename all callbackInterface.handleEvent methods to something which describes what the method is about bugzilla@jessica.w3.org
- [Bug 14761] New: Drop =FunctionOnly from everywhere else than interface Function bugzilla@jessica.w3.org
- [Bug 14760] New: Drop =FunctionOnly from NavigatorUserMediaErrorCallback bugzilla@jessica.w3.org
- [Bug 14759] New: Rename NavigatorUserMediaErrorCallback.handleEvent bugzilla@jessica.w3.org
- [Bug 14758] New: Drop =FunctionOnly from NavigatorUserMediaSuccessCallback bugzilla@jessica.w3.org
- [Bug 14757] New: Rename NavigatorUserMediaSuccessCallback.handleEvent bugzilla@jessica.w3.org
- [Bug 14756] New: Drop =FunctionOnly from FunctionStringCallback bugzilla@jessica.w3.org
- [Bug 14755] New: rename FunctionStringCallback::handleEvent bugzilla@jessica.w3.org
- [Bug 14726] Add an attribute "language" to the math tag. Example values would be "MathML" or "AMS-LaTeX". LaTeX is widely used in Wikipedia math formulae; so maybe it would be nice to have this client-side. bugzilla@jessica.w3.org
- [Bug 14738] Please add more canvas examples bugzilla@jessica.w3.org
- [Bug 14747] mostrar tudo que tem bugzilla@jessica.w3.org
- [Bug 14737] CANVAS is awesome!!!!1 bugzilla@jessica.w3.org
- [Bug 14753] You guys succeed on this way. Abobe gave up in this. You are armed. bugzilla@jessica.w3.org
- [Bug 14754] New: <track> rename cueAsSource to text for consistency bugzilla@jessica.w3.org
- [Bug 14753] New: You guys succeed on this way. Abobe gave up in this. You are armed. bugzilla@jessica.w3.org
- [Bug 14750] New: Clarify what the origin of the new document is if the document is blown away (consider if the old document set document.domain) bugzilla@jessica.w3.org
- [Bug 14337] Drag-and-drop / undo manager interaction bugzilla@jessica.w3.org
- [Bug 14337] Drag-and-drop / undo manager interaction bugzilla@jessica.w3.org
- [Bug 14740] title attribute definition does not match reality bugzilla@jessica.w3.org
- [Bug 12393] Add "allow-popups" for iframe@sandbox bugzilla@jessica.w3.org
- [Bug 12393] Add "allow-popups" for iframe@sandbox bugzilla@jessica.w3.org
- [Bug 12393] Add "allow-popups" for iframe@sandbox bugzilla@jessica.w3.org
Wednesday, 9 November 2011
Tuesday, 8 November 2011
Monday, 7 November 2011
Sunday, 6 November 2011
Saturday, 5 November 2011
Friday, 4 November 2011
Thursday, 3 November 2011
- [Bug 13558] input type=email should support friendly names bugzilla@jessica.w3.org
- [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration bugzilla@jessica.w3.org
- [Bug 14689] xml-stylesheet with type=text/xsl needs to be handled explicitly bugzilla@jessica.w3.org
- [Bug 13558] input type=email should support friendly names bugzilla@jessica.w3.org
- [Bug 14689] xml-stylesheet with type=text/xsl needs to be handled explicitly bugzilla@jessica.w3.org
- [Bug 13558] input type=email should support friendly names bugzilla@jessica.w3.org
- [Bug 13570] why does input type=color support autocomplete? bugzilla@jessica.w3.org
- [Bug 13570] why does input type=color support autocomplete? bugzilla@jessica.w3.org
- [Bug 13570] why does input type=color support autocomplete? bugzilla@jessica.w3.org
- [Bug 13550] type table in 4.10.7 should indicate control type changes based on list attribute bugzilla@jessica.w3.org
- [Bug 13558] input type=email should support friendly names bugzilla@jessica.w3.org
- [Bug 14691] <a> should be allowed as a child of <dl> Current browsers allow this already. A semantic use case is file downlads <dl><a href="filename1.pdf"><dt>Filename</dt><dd>description of file</dd><dd>filetype</dd></a>etc...</dl>. bugzilla@jessica.w3.org
- [Bug 14690] <a> should be allowed as a child of <dl> Current browsers allow this already. A semantic use case is file downlads <dl><a href="filename1.pdf"><dt>Filename</dt><dd>description of file</dd><dd>filetype</dd></a>etc...</dl>. bugzilla@jessica.w3.org
- [Bug 14690] <a> should be allowed as a child of <dl> Current browsers allow this already. A semantic use case is file downlads <dl><a href="filename1.pdf"><dt>Filename</dt><dd>description of file</dd><dd>filetype</dd></a>etc...</dl>. bugzilla@jessica.w3.org
- [Bug 14690] <a> should be allowed as a child of <dl> Current browsers allow this already. A semantic use case is file downlads <dl><a href="filename1.pdf"><dt>Filename</dt><dd>description of file</dd><dd>filetype</dd></a>etc...</dl>. bugzilla@jessica.w3.org
- [Bug 13359] A way is needed to identify the type of data in a track element bugzilla@jessica.w3.org
- [Bug 13550] type table in 4.10.7 should indicate control type changes based on list attribute bugzilla@jessica.w3.org
- [Bug 13357] <video>: Additional AudioTrack.kind categories are needed to identify tracks where audio descriptions are premixed with main dialogue. bugzilla@jessica.w3.org
- [Bug 13239] Add support for in-page dialogs bugzilla@jessica.w3.org
- [Bug 12409] WF3: Automatic capitalization in input fields bugzilla@jessica.w3.org
- [Bug 12885] WF3: Provide a way for the author to specify what kind of keyboard behaviour to use for text inputs on multimodal keyboards (e.g. show the numeric keyboard, capitalise the first character by default, etc) bugzilla@jessica.w3.org
- [Bug 13359] A way is needed to identify the type of data in a track element bugzilla@jessica.w3.org
- [Bug 13558] input type=email should support friendly names bugzilla@jessica.w3.org
- [Bug 14691] New: <a> should be allowed as a child of <dl> Current browsers allow this already. A semantic use case is file downlads <dl><a href="filename1.pdf"><dt>Filename</dt><dd>description of file</dd><dd>filetype</dd></a>etc...</dl>. bugzilla@jessica.w3.org
- [Bug 13551] clarify definition of "value sanitization algorithm" bugzilla@jessica.w3.org
- [Bug 13551] clarify definition of "value sanitization algorithm" bugzilla@jessica.w3.org
- [Bug 13359] A way is needed to identify the type of data in a track element bugzilla@jessica.w3.org
- [Bug 14690] New: <a> should be allowed as a child of <dl> Current browsers allow this already. A semantic use case is file downlads <dl><a href="filename1.pdf"><dt>Filename</dt><dd>description of file</dd><dd>filetype</dd></a>etc...</dl>. bugzilla@jessica.w3.org
- [Bug 12544] <video> MEDIA CONTROLLER requires track kind for in-band tracks bugzilla@jessica.w3.org
- [Bug 13357] <video>: Additional AudioTrack.kind categories are needed to identify tracks where audio descriptions are premixed with main dialogue. bugzilla@jessica.w3.org
- [Bug 13986] Update vCard vocabulary to RFC6350 bugzilla@jessica.w3.org
- [Bug 13986] Update vCard vocabulary to RFC6350 bugzilla@jessica.w3.org
- [Bug 14688] fhfhgfhgfhgfhgfhgfhgfhgfhg giuhgiuhiuhi hbkhikhiuhbi ihbihbjhbjhb bugzilla@jessica.w3.org
- [Bug 14689] New: xml-stylesheet with type=text/xsl needs to be handled explicitly bugzilla@jessica.w3.org
- [Bug 14526] WF2: When adding filenames to the data set, should there be normalization of decomposed forms? bugzilla@jessica.w3.org
- [Bug 12547] <video> MEDIA CONTROLLER requires readyState for grouped multitrack bugzilla@jessica.w3.org
- [Bug 14688] New: fhfhgfhgfhgfhgfhgfhgfhgfhg giuhgiuhiuhi hbkhikhiuhbi ihbihbjhbjhb bugzilla@jessica.w3.org
- [Bug 12715] When used to include data blocks (as opposed to scripts), the data must be embedded inline bugzilla@jessica.w3.org
- [Bug 13983] WF2: It seems like textarea's raw value should always normalize newlines to \n bugzilla@jessica.w3.org
- [Bug 14260] <track> "text tracks ready" and HTMLMediaElement.readyState bugzilla@jessica.w3.org
- [Bug 13983] WF2: It seems like textarea's raw value should always normalize newlines to \n bugzilla@jessica.w3.org
- [Bug 13995] <track> Don't check Content-Type for <track> bugzilla@jessica.w3.org
- [Bug 13995] <track> Don't check Content-Type for <track> bugzilla@jessica.w3.org
- [Bug 14681] Separate 'acknowledgements' into list by participants of WHATWG and the W3C HTML Working Group? It may be useful to see all of the members who contribute in each/both group for clarification purposes. bugzilla@jessica.w3.org
- [Bug 14682] Listed, submittable, bugzilla@jessica.w3.org
- [Bug 12547] <video> MEDIA CONTROLLER requires readyState for grouped multitrack bugzilla@jessica.w3.org
- [Bug 13995] <track> Don't check Content-Type for <track> bugzilla@jessica.w3.org
- [Bug 11984] Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org
- [Bug 14104] Video: Streaming text support in <track> element bugzilla@jessica.w3.org
- [Bug 14174] onerror: if body can't be parsed then window.onerror should be invoked bugzilla@jessica.w3.org
- [Bug 14175] onerror: Defer firing the onerror from compiling an event handler until it's used bugzilla@jessica.w3.org
- [Bug 14176] onerror: If the script is not same-origin, window.onerror should be invoked with arguments ("Script error.", "", 0) bugzilla@jessica.w3.org
- [Bug 14177] onerror: If the script is not same-origin, window.onerror should be invoked with arguments ("Script error.", "", 0) bugzilla@jessica.w3.org
- [Bug 14182] onerror: setTimeout("{", 10) and window.onerror bugzilla@jessica.w3.org
- [Bug 14260] <track> "text tracks ready" and HTMLMediaElement.readyState bugzilla@jessica.w3.org
- [Bug 14284] Need HTML parser algorithm options bugzilla@jessica.w3.org
- [Bug 14364] appcache: Add an API to make appcache support caching specific URLs dynamically bugzilla@jessica.w3.org
- [Bug 14358] <track> and WebVTT cue.alignment need more values bugzilla@jessica.w3.org
- [Bug 14364] appcache: Add an API to make appcache support caching specific URLs dynamically bugzilla@jessica.w3.org
- [Bug 14427] Investigate if click()'s click-in-progress should apply to user and/or script initiated clicks bugzilla@jessica.w3.org
- [Bug 14470] Microdata: Language handling bugzilla@jessica.w3.org
- [Bug 14499] Need ability to reset Canvas clipping region without resetting all other Canvas state bugzilla@jessica.w3.org
- [Bug 14686] I'm a little worried about deprecating nearly all the table attributes. I have a web application which I have worked on for the past 5 years, I have already started incorporating HTML5 into it. But, if support for tables is removed, my web application w bugzilla@jessica.w3.org
- [Bug 14687] uhi u hiu hiuh ih ihih hhiuhiu hhhhih hh oih iuh iho hoih h oi bugzilla@jessica.w3.org
- [Bug 14526] WF2: When adding filenames to the data set, should there be normalization of decomposed forms? bugzilla@jessica.w3.org
- [Bug 14687] New: uhi u hiu hiuh ih ihih hhiuhiu hhhhih hh oih iuh iho hoih h oi bugzilla@jessica.w3.org
- [Bug 14686] New: I'm a little worried about deprecating nearly all the table attributes. I have a web application which I have worked on for the past 5 years, I have already started incorporating HTML5 into it. But, if support for tables is removed, my web application w bugzilla@jessica.w3.org
- [Bug 10694] Specify window.console bugzilla@jessica.w3.org
- [Bug 11984] Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org
- [Bug 13240] Consider replacing <time> with <data> bugzilla@jessica.w3.org
- [Bug 13240] Consider replacing <time> with <data> bugzilla@jessica.w3.org
- [Bug 13240] Consider replacing <time> with <data> bugzilla@jessica.w3.org
- [Bug 13240] Consider replacing <time> with <data> bugzilla@jessica.w3.org
- [Bug 14683] this site is very good bugzilla@jessica.w3.org
- [Bug 14683] New: this site is very good bugzilla@jessica.w3.org
- [Bug 14548] Grouping Content: algorithm for incrementing value (OL->LI @value) does not match any current user agent bugzilla@jessica.w3.org
- [Bug 13240] Consider replacing <time> with <data> bugzilla@jessica.w3.org
- [Bug 12393] Add "allow-popups" for iframe@sandbox bugzilla@jessica.w3.org
- [Bug 14682] New: Listed, submittable, bugzilla@jessica.w3.org
- [Bug 13240] Consider replacing <time> with <data> bugzilla@jessica.w3.org
Wednesday, 2 November 2011
- [Bug 14678] <video> is in the-iframe-element.html bugzilla@jessica.w3.org
- [Bug 14681] New: Separate 'acknowledgements' into list by participants of WHATWG and the W3C HTML Working Group? It may be useful to see all of the members who contribute in each/both group for clarification purposes. bugzilla@jessica.w3.org
- [Bug 12547] <video> MEDIA CONTROLLER requires readyState for grouped multitrack bugzilla@jessica.w3.org
- [Bug 14548] Grouping Content: algorithm for incrementing value (OL->LI @value) does not match any current user agent bugzilla@jessica.w3.org
- [Bug 14601] Investigate if support for <a> inside image maps should be brought back to HTML bugzilla@jessica.w3.org
- [Bug 14104] Video: Streaming text support in <track> element bugzilla@jessica.w3.org
- [Bug 14575] <track> Spec is confused about which edge the text position starts from bugzilla@jessica.w3.org
- [Bug 14581] Multiline text on canvas bugzilla@jessica.w3.org
- [Bug 14596] Microdata: validity contraints to catch missing attributes bugzilla@jessica.w3.org
- [Bug 14601] Investigate if support for <a> inside image maps should be brought back to HTML bugzilla@jessica.w3.org
- [Bug 14630] This sentence is rather confusing, it seems to indicate that <data> should be used with data-*, or can be replaced by data-*: "The element can also, however, be used in conjunction with scripts in the page, for when a script has store a literal value alon bugzilla@jessica.w3.org
- [Bug 14646] <track> Don't use one-letter settings. They are non-intuitive and hard to remember. It makes little sense to use a single letter for the setting but then a sensible string for the value. Please use "align" instead of "A", etc. bugzilla@jessica.w3.org
- [Bug 14661] I find the compositing section unclear with regard to partial transparency. E.g., under "a atop b", if a is partially transparent, does b show through? bugzilla@jessica.w3.org
- [Bug 14674] 1. Please consider adding those API for Round-Trip measurments. 2.Clients might wish to detected server hangs and re-connect... bugzilla@jessica.w3.org
- [Bug 14526] WF2: When adding filenames to the data set, should there be normalization of decomposed forms? bugzilla@jessica.w3.org
- [Bug 14676] For UTF-16, the oder of the steps in "change the encoding" doesn't seem right. bugzilla@jessica.w3.org
- [Bug 14676] For UTF-16, the oder of the steps in "change the encoding" doesn't seem right. bugzilla@jessica.w3.org
- [Bug 14678] <video> is in the-iframe-element.html bugzilla@jessica.w3.org
- [Bug 14679] Consider replacing <data value> with a global attribute itemvalue="" bugzilla@jessica.w3.org
- [Bug 14104] Video: Streaming text support in <track> element bugzilla@jessica.w3.org
- [Bug 11124] consider reducing verbosity when talking about code points bugzilla@jessica.w3.org
- [Bug 12399] <video> Expose statistics for media elements bugzilla@jessica.w3.org
- [Bug 14104] Video: Streaming text support in <track> element bugzilla@jessica.w3.org
- [Bug 13995] <track> Don't check Content-Type for <track> bugzilla@jessica.w3.org
- [Bug 13986] Update vCard vocabulary to RFC6350 bugzilla@jessica.w3.org
- [Bug 13983] WF2: It seems like textarea's raw value should always normalize newlines to \n bugzilla@jessica.w3.org
- [Bug 13769] WF3: Add trim="" attribute to <input type=text/search> that strips leading and trailing whitespace from the value bugzilla@jessica.w3.org
- [Bug 13608] Add <menuitem> element bugzilla@jessica.w3.org
- [Bug 14492] <video> change event when tracks are removed bugzilla@jessica.w3.org
- [Bug 13358] <video> also fire a 'change' event at VideoTrackList, AudioTrackList, and TextTrackList objects when their list of tracks changes bugzilla@jessica.w3.org
- [Bug 13357] <video>: Additional AudioTrack.kind categories are needed to identify tracks where audio descriptions are premixed with main dialogue. bugzilla@jessica.w3.org
- [Bug 13239] Add support for in-page dialogs bugzilla@jessica.w3.org
- [Bug 13113] Parsing algorithm should not preclude Complex Ruby bugzilla@jessica.w3.org
- [Bug 11482] WF2: Change accept="" to accept file extensions as well as MIME types (maybe based on whether they start with a period) bugzilla@jessica.w3.org
- [Bug 12885] WF3: Provide a way for the author to specify what kind of keyboard behaviour to use for text inputs on multimodal keyboards (e.g. show the numeric keyboard, capitalise the first character by default, etc) bugzilla@jessica.w3.org
- [Bug 12612] [registries] make rel value prohibitions in the spec and microformats wiki match bugzilla@jessica.w3.org
- [Bug 12544] <video> MEDIA CONTROLLER requires track kind for in-band tracks bugzilla@jessica.w3.org
- [Bug 12409] WF3: Automatic capitalization in input fields bugzilla@jessica.w3.org
- [Bug 12399] <video> Expose statistics for media elements bugzilla@jessica.w3.org
- [Bug 11984] Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org
- [Bug 11482] WF2: Change accept="" to accept file extensions as well as MIME types (maybe based on whether they start with a period) bugzilla@jessica.w3.org
- [Bug 11124] consider reducing verbosity when talking about code points bugzilla@jessica.w3.org
- [Bug 12943] Drop progress.position IDL or make it settable bugzilla@jessica.w3.org
- [Bug 10830] i18n comment : Please add support for rb bugzilla@jessica.w3.org
- [Bug 13995] <track> Don't check Content-Type for <track> bugzilla@jessica.w3.org
- [Bug 12399] <video> Expose statistics for media elements bugzilla@jessica.w3.org
- [Bug 14260] <track> "text tracks ready" and HTMLMediaElement.readyState bugzilla@jessica.w3.org
- [Bug 11482] WF2: Change accept="" to accept file extensions as well as MIME types (maybe based on whether they start with a period) bugzilla@jessica.w3.org
- [Bug 13608] Add <menuitem> element bugzilla@jessica.w3.org
- [Bug 14552] <track> support // and /* */ comments everywhere except in the signature line bugzilla@jessica.w3.org
- [Bug 13113] Parsing algorithm should not preclude Complex Ruby bugzilla@jessica.w3.org
- [Bug 13239] Add support for in-page dialogs bugzilla@jessica.w3.org
- [Bug 14363] Update the registration mechanisms bugzilla@jessica.w3.org
- [Bug 14284] Need HTML parser algorithm options bugzilla@jessica.w3.org
- [Bug 14548] Grouping Content: algorithm for incrementing value (OL->LI @value) does not match any current user agent bugzilla@jessica.w3.org
- [Bug 13769] WF3: Add trim="" attribute to <input type=text/search> that strips leading and trailing whitespace from the value bugzilla@jessica.w3.org
- [Bug 14596] Microdata: validity contraints to catch missing attributes bugzilla@jessica.w3.org
- [Bug 14104] Video: Streaming text support in <track> element bugzilla@jessica.w3.org
- [Bug 13791] Rename SignalingCallback interface to PeerConnectionSignalingCallback for consistency bugzilla@jessica.w3.org
- [Bug 12885] WF3: Provide a way for the author to specify what kind of keyboard behaviour to use for text inputs on multimodal keyboards (e.g. show the numeric keyboard, capitalise the first character by default, etc) bugzilla@jessica.w3.org
- [Bug 12409] WF3: Automatic capitalization in input fields bugzilla@jessica.w3.org
- [Bug 14364] appcache: Add an API to make appcache support caching specific URLs dynamically bugzilla@jessica.w3.org
- [Bug 14358] <track> and WebVTT cue.alignment need more values bugzilla@jessica.w3.org
- [Bug 13986] Update vCard vocabulary to RFC6350 bugzilla@jessica.w3.org
- [Bug 14526] WF2: When adding filenames to the data set, should there be normalization of decomposed forms? bugzilla@jessica.w3.org
- [Bug 11124] consider reducing verbosity when talking about code points bugzilla@jessica.w3.org
- [Bug 14499] Need ability to reset Canvas clipping region without resetting all other Canvas state bugzilla@jessica.w3.org
- [Bug 14586] Microdata: inconsistency between itemType, getItems and JSON regarding absolute URLs bugzilla@jessica.w3.org
- [Bug 13718] specification should not require language-specific quotation styles without defining them bugzilla@jessica.w3.org
- [Bug 14586] Microdata: inconsistency between itemType, getItems and JSON regarding absolute URLs bugzilla@jessica.w3.org
- [Bug 13398] i18n-ISSUE-80: Default rules for the quotes property bugzilla@jessica.w3.org
- [Bug 13398] i18n-ISSUE-80: Default rules for the quotes property bugzilla@jessica.w3.org
- [Bug 14679] Consider replacing <data value> with a global attribute itemvalue="" bugzilla@jessica.w3.org
- [Bug 13240] Consider replacing <time> with <data> bugzilla@jessica.w3.org
- [Bug 14679] New: Consider replacing <data value> with a global attribute itemvalue="" bugzilla@jessica.w3.org
- [Bug 13240] Consider replacing <time> with <data> bugzilla@jessica.w3.org
- [Bug 14492] <video> change event when tracks are removed bugzilla@jessica.w3.org
- [Bug 13240] Consider replacing <time> with <data> bugzilla@jessica.w3.org
- [Bug 13240] Consider replacing <time> with <data> bugzilla@jessica.w3.org
- [Bug 13240] Consider replacing <time> with <data> bugzilla@jessica.w3.org
- [Bug 13240] Consider replacing <time> with <data> bugzilla@jessica.w3.org
- [Bug 13240] Consider replacing <time> with <data> bugzilla@jessica.w3.org
- [Bug 13240] Consider replacing <time> with <data> bugzilla@jessica.w3.org
- [Bug 13240] Consider replacing <time> with <data> bugzilla@jessica.w3.org
- [Bug 13240] Consider replacing <time> with <data> bugzilla@jessica.w3.org
- [Bug 14536] <track> Characters in the range 0-9, a-Z can simply be one of "ampltg" as those are the only characters that matter. bugzilla@jessica.w3.org
- [Bug 13240] Consider replacing <time> with <data> bugzilla@jessica.w3.org
- [Bug 14678] New: <video> is in the-iframe-element.html bugzilla@jessica.w3.org
- [Bug 14676] For UTF-16, the oder of the steps in "change the encoding" doesn't seem right. bugzilla@jessica.w3.org
- [Bug 14646] <track> Don't use one-letter settings. They are non-intuitive and hard to remember. It makes little sense to use a single letter for the setting but then a sensible string for the value. Please use "align" instead of "A", etc. bugzilla@jessica.w3.org
- [Bug 14676] New: For UTF-16, the oder of the steps in "change the encoding" doesn't seem right. bugzilla@jessica.w3.org
- [Bug 14548] Grouping Content: algorithm for incrementing value (OL->LI @value) does not match any current user agent bugzilla@jessica.w3.org
- [Bug 14672] What is this site...? i think it looks helpful but i am confused... :-( bugzilla@jessica.w3.org
- [Bug 14674] New: 1. Please consider adding those API for Round-Trip measurments. 2.Clients might wish to detected server hangs and re-connect... bugzilla@jessica.w3.org
- [Bug 14672] New: What is this site...? i think it looks helpful but i am confused... :-( bugzilla@jessica.w3.org
- [Bug 14526] WF2: When adding filenames to the data set, should there be normalization of decomposed forms? bugzilla@jessica.w3.org
Tuesday, 1 November 2011
- [Bug 14646] <track> Don't use one-letter settings. They are non-intuitive and hard to remember. It makes little sense to use a single letter for the setting but then a sensible string for the value. Please use "align" instead of "A", etc. bugzilla@jessica.w3.org
- [Bug 14586] Microdata: inconsistency between itemType, getItems and JSON regarding absolute URLs bugzilla@jessica.w3.org
- [Bug 14499] Need ability to reset Canvas clipping region without resetting all other Canvas state bugzilla@jessica.w3.org
- [Bug 14499] Need ability to reset Canvas clipping region without resetting all other Canvas state bugzilla@jessica.w3.org
- [Bug 14646] <track> Don't use one-letter settings. They are non-intuitive and hard to remember. It makes little sense to use a single letter for the setting but then a sensible string for the value. Please use "align" instead of "A", etc. bugzilla@jessica.w3.org
- [Bug 14649] "Create n new WebVTT Internal Node Object" s/n/a/? bugzilla@jessica.w3.org
- [Bug 14650] 'If the dropped is false or it the current drag operation is "none"' s/the//, s/or it/or if/ bugzilla@jessica.w3.org
- [Bug 13398] i18n-ISSUE-80: Default rules for the quotes property bugzilla@jessica.w3.org
- [Bug 13718] specification should not require language-specific quotation styles without defining them bugzilla@jessica.w3.org
- [Bug 13398] i18n-ISSUE-80: Default rules for the quotes property bugzilla@jessica.w3.org
- [Bug 13398] i18n-ISSUE-80: Default rules for the quotes property bugzilla@jessica.w3.org
- [Bug 14661] New: I find the compositing section unclear with regard to partial transparency. E.g., under "a atop b", if a is partially transparent, does b show through? bugzilla@jessica.w3.org
- [Bug 14572] <track> Collect space characters and discard them after step 8. bugzilla@jessica.w3.org
- [Bug 14499] Need ability to reset Canvas clipping region without resetting all other Canvas state bugzilla@jessica.w3.org
- [Bug 14575] <track> The computed x-position should use the computed size when aligning - not 100 bugzilla@jessica.w3.org
- [Bug 14492] <video> change event when tracks are removed bugzilla@jessica.w3.org
- [Bug 14526] WF2: When adding filenames to the data set, should there be normalization of decomposed forms? bugzilla@jessica.w3.org
- [Bug 14499] Need ability to reset Canvas clipping region without resetting all other Canvas state bugzilla@jessica.w3.org
- [Bug 14526] WF2: When adding filenames to the data set, should there be normalization of decomposed forms? bugzilla@jessica.w3.org
- [Bug 14548] Grouping Content: algorithm for incrementing value (OL->LI @value) does not match any current user agent bugzilla@jessica.w3.org
- [Bug 14570] <track> In section 4.8.10.12.1/"A line position"/"text track cue computed line position" algorithm: It seems better to let the step 5 be "Increment n by one" bugzilla@jessica.w3.org
- [Bug 14570] <track> In section 4.8.10.12.1/"A line position"/"text track cue computed line position" algorithm: It seems better to let the step 5 be "Increment n by one" bugzilla@jessica.w3.org
- [Bug 14570] <track> In section 4.8.10.12.1/"A line position"/"text track cue computed line position" algorithm: It seems better to let the step 5 be "Increment n by one" bugzilla@jessica.w3.org
- [Bug 14574] <track> The text track cue alignment setting should map to a CSS property ('text-align') bugzilla@jessica.w3.org
- [Bug 14574] <track> The text track cue alignment setting should map to a CSS property ('text-align') bugzilla@jessica.w3.org
- [Bug 14575] <track> The computed x-position should use the computed size when aligning - not 100 bugzilla@jessica.w3.org
- [Bug 11203] Canvas security model does not allow for same-origin relaxation bugzilla@jessica.w3.org
- [Bug 10787] Add a way to get a File/Blob from a <canvas> bugzilla@jessica.w3.org
- [Bug 14579] Add ellipse support to canvas bugzilla@jessica.w3.org
- [Bug 11739] I would like to see a clearPath or clearStroke functions similar to clearRect but to clear lines, not just full rectangles bugzilla@jessica.w3.org
- [Bug 9236] Add Path objects and intersects() function bugzilla@jessica.w3.org
- [Bug 14579] Add ellipse support to canvas bugzilla@jessica.w3.org
- [Bug 14586] Microdata: inconsistency between itemType, getItems and JSON regarding absolute URLs bugzilla@jessica.w3.org
- [Bug 14586] Microdata: inconsistency between itemType, getItems and JSON regarding absolute URLs bugzilla@jessica.w3.org
- [Bug 14601] Investigate if support for <a> inside image maps should be brought back to HTML bugzilla@jessica.w3.org
- [Bug 14628] <track> In step 6-7, only consume the character if it is a ':' bugzilla@jessica.w3.org
- [Bug 14628] <track> In step 6-7, only consume the character if it is a ':' bugzilla@jessica.w3.org
- [Bug 14651] i think the websocket garbage collection rules might need tweaking now that message can't be fired in CLOSING (can error be fired in CLOSING?) bugzilla@jessica.w3.org
- [Bug 14651] i think the websocket garbage collection rules might need tweaking now that message can't be fired in CLOSING (can error be fired in CLOSING?) bugzilla@jessica.w3.org
- [Bug 14653] 85130dl4dzz bugzilla@jessica.w3.org
- [Bug 14646] <track> Don't use one-letter settings. They are non-intuitive and hard to remember. It makes little sense to use a single letter for the setting but then a sensible string for the value. Please use "align" instead of "A", etc. bugzilla@jessica.w3.org
- [Bug 13240] Consider replacing <time> with <data> bugzilla@jessica.w3.org
- [Bug 14651] i think the websocket garbage collection rules might need tweaking now that message can't be fired in CLOSING (can error be fired in CLOSING?) bugzilla@jessica.w3.org
- [Bug 14638] Should a canceled drop event signify a failed drop operation? bugzilla@jessica.w3.org
- [Bug 14649] "Create n new WebVTT Internal Node Object" s/n/a/? bugzilla@jessica.w3.org
- [Bug 14650] 'If the dropped is false or it the current drag operation is "none"' s/the//, s/or it/or if/ bugzilla@jessica.w3.org
- [Bug 14638] Should a canceled drop event signify a failed drop operation? bugzilla@jessica.w3.org
- [Bug 14650] 'If the dropped is false or it the current drag operation is "none"' s/the//, s/or it/or if/ bugzilla@jessica.w3.org
- [Bug 14654] typo: "data procesors" bugzilla@jessica.w3.org
- [Bug 14649] "Create n new WebVTT Internal Node Object" s/n/a/? bugzilla@jessica.w3.org
- [Bug 14651] i think the websocket garbage collection rules might need tweaking now that message can't be fired in CLOSING (can error be fired in CLOSING?) bugzilla@jessica.w3.org
- [Bug 14654] typo: "data procesors" bugzilla@jessica.w3.org
- [Bug 14655] More typos in http://html5.org/r/6798 bugzilla@jessica.w3.org
- [Bug 14650] 'If the dropped is false or it the current drag operation is "none"' s/the//, s/or it/or if/ bugzilla@jessica.w3.org
- [Bug 14655] More typos in http://html5.org/r/6798 bugzilla@jessica.w3.org
- [Bug 14655] New: More typos in http://html5.org/r/6798 bugzilla@jessica.w3.org
- [Bug 14654] New: typo: "data procesors" bugzilla@jessica.w3.org
- [Bug 14637] Is itemtype="" valid? bugzilla@jessica.w3.org
- [Bug 14601] Investigate if support for <a> inside image maps should be brought back to HTML bugzilla@jessica.w3.org
- [Bug 14653] 85130dl4dzz bugzilla@jessica.w3.org
- [Bug 14653] New: 85130dl4dzz bugzilla@jessica.w3.org
- [Bug 14601] Investigate if support for <a> inside image maps should be brought back to HTML bugzilla@jessica.w3.org
- [Bug 14601] Investigate if support for <a> inside image maps should be brought back to HTML bugzilla@jessica.w3.org
- [Bug 14637] Is itemtype="" valid? bugzilla@jessica.w3.org
- [Bug 14651] New: i think the websocket garbage collection rules might need tweaking now that message can't be fired in CLOSING (can error be fired in CLOSING?) bugzilla@jessica.w3.org
- [Bug 14646] <track> Don't use one-letter settings. They are non-intuitive and hard to remember. It makes little sense to use a single letter for the setting but then a sensible string for the value. Please use "align" instead of "A", etc. bugzilla@jessica.w3.org
- [Bug 14650] New: 'If the dropped is false or it the current drag operation is "none"' s/the//, s/or it/or if/ bugzilla@jessica.w3.org
- [Bug 14649] New: "Create n new WebVTT Internal Node Object" s/n/a/? bugzilla@jessica.w3.org
- [Bug 14570] <track> In section 4.8.10.12.1/"A line position"/"text track cue computed line position" algorithm: It seems better to let the step 5 be "Increment n by one" bugzilla@jessica.w3.org
- [Bug 14648] How can I get a microdata? after test with HTML5 no point for MICRODATA bugzilla@jessica.w3.org
- [Bug 14648] New: How can I get a microdata? after test with HTML5 no point for MICRODATA bugzilla@jessica.w3.org
- [Bug 14565] Chain of normative statements connecting MIME type to HTML vs. XHTML is broken or unobvious bugzilla@jessica.w3.org
- [Bug 14570] <track> In section 4.8.10.12.1/"A line position"/"text track cue computed line position" algorithm: It seems better to let the step 5 be "Increment n by one" bugzilla@jessica.w3.org
- [Bug 14572] <track> Collect space characters and discard them after step 8. bugzilla@jessica.w3.org
- [Bug 14571] <track> allow signature to be followed by FF for consistency in the parser bugzilla@jessica.w3.org
- [Bug 14572] <track> Collect space characters and discard them after step 8. bugzilla@jessica.w3.org
- [Bug 14573] Make so you can put <hr> inside <select>. Many times I've seen people use hacks such as <input disabled>--------</input> as a separator/divider in select. For people who want to have a selection with no default value preselected. Example: <select> <opti bugzilla@jessica.w3.org
- [Bug 14577] "state changed is true, fire a popstate event" -- missing "If" bugzilla@jessica.w3.org
- [Bug 14577] "state changed is true, fire a popstate event" -- missing "If" bugzilla@jessica.w3.org
- [Bug 14579] Add ellipse support to canvas bugzilla@jessica.w3.org
- [Bug 14581] Multiline text on canvas bugzilla@jessica.w3.org
- [Bug 14581] filing a separate feature request as requested in http://www.w3.org/Bugs/Public/show_bug.cgi?id=14562 --- Please add support for multiline text. more people than you think want to use graphics-manipulable text on their canvas. As the graphics contact for bugzilla@jessica.w3.org
- [Bug 14586] Microdata: inconsistency between itemType, getItems and JSON regarding absolute URLs bugzilla@jessica.w3.org
- [Bug 14601] Investigate if support for <a> inside image maps should be brought back to HTML bugzilla@jessica.w3.org
- [Bug 14600] Spec element.setCapture / document.releaseCapture bugzilla@jessica.w3.org
- [Bug 14638] Should a canceled drop event signify a failed drop operation? bugzilla@jessica.w3.org
- [Bug 14631] Capitalization of Microformats (should be microformats) bugzilla@jessica.w3.org
- [Bug 14631] Capitalization of Microformats (should be microformats) bugzilla@jessica.w3.org
- [Bug 14580] filing a separate feature request as requested in http://www.w3.org/Bugs/Public/show_bug.cgi?id=14562 --- Please add a more elaborate font metrics object such as currently shimmed on https://github.com/Pomax/fontmetrics.js, so that graphics involving text bugzilla@jessica.w3.org
- [Bug 7798] More data from TextMetrics API bugzilla@jessica.w3.org
- [Bug 14537] <track> The string "<." creates a start tag with no name and an empty string class. Is that really what we want? bugzilla@jessica.w3.org
- [Bug 14638] Should a canceled drop event signify a failed drop operation? bugzilla@jessica.w3.org
- [Bug 14552] <track> support // and /* */ comments everywhere except in the signature line bugzilla@jessica.w3.org
- [Bug 14537] <track> The string "<." creates a start tag with no name and an empty string class. Is that really what we want? bugzilla@jessica.w3.org
- [Bug 14629] s/has store/has stored/? bugzilla@jessica.w3.org
- [Bug 14630] This sentence is rather confusing, it seems to indicate that <data> should be used with data-*, or can be replaced by data-*: "The element can also, however, be used in conjunction with scripts in the page, for when a script has store a literal value alon bugzilla@jessica.w3.org
- [Bug 14629] s/has store/has stored/? bugzilla@jessica.w3.org
- [Bug 14631] Capitalization of Microformats (should be microformats) bugzilla@jessica.w3.org
- [Bug 14633] Drag source and drag destination can't coordinate behavior. bugzilla@jessica.w3.org
- [Bug 14637] Is itemtype="" valid? bugzilla@jessica.w3.org
- [Bug 14637] Is itemtype="" valid? bugzilla@jessica.w3.org
- [Bug 14638] Should a canceled drop event signify a failed drop operation? bugzilla@jessica.w3.org
- [Bug 14628] <track> In step 6-7, only consume the character if it is a ':' bugzilla@jessica.w3.org
- [Bug 14646] <track> Don't use one-letter settings. They are non-intuitive and hard to remember. It makes little sense to use a single letter for the setting but then a sensible string for the value. Please use "align" instead of "A", etc. bugzilla@jessica.w3.org
Last message date: Wednesday, 30 November 2011 21:28:41 UTC