public-html-bugzilla@w3.org from July 2010: by date

Saturday, 31 July 2010
- [Bug 10278] New: element.hidden doesn't always return the Hidden facet; e.g. on <label>s. We should make that clearer. bugzilla@jessica.w3.org
- [Bug 10276] New: Can we change this back into a boolean again? I know I requested it to be compatible with contentEditable, but the one implementor never picked up the change and this will now cause problems with editors e.g. TinyMCE. bugzilla@jessica.w3.org
- [Bug 10248] Canvas requires a Caret Drawing call method bugzilla@jessica.w3.org
Friday, 30 July 2010
- [Bug 10274] New: The sentence starting "On setting, if the new value is true" seems to be out of place. Also raising a syntax_err is not web compatible and breaks at least TinyMCE. bugzilla@jessica.w3.org
- [Bug 10267] What happens if you delete an attribute? For the following test case, Chrome outputs "string undefined", while Firefox and Opera give "string string": data:text/html,<!doctype html><script>var el = document.createElement("a"); var type = typeof el.id; de bugzilla@jessica.w3.org
- [Bug 10268] New: baa baa blacksheep bugzilla@jessica.w3.org
- [Bug 10267] What happens if you delete an attribute? For the following test case, Chrome outputs "string undefined", while Firefox and Opera give "string string": data:text/html,<!doctype html><script>var el = document.createElement("a"); var type = typeof el.id; de bugzilla@jessica.w3.org
- [Bug 10267] New: What happens if you delete an attribute? For the following test case, Chrome outputs "string undefined", while Firefox and Opera give "string string": data:text/html,<!doctype html><script>var el = document.createElement("a"); var type = typeof el.id; de bugzilla@jessica.w3.org
Thursday, 29 July 2010
- [Bug 10266] "contexts in which this element may be used:" should read "where flow content or phrasing content is expected" bugzilla@jessica.w3.org
- [Bug 10266] New: "contexts in which this element may be used:" should read "where flow content or phrasing content is expected" bugzilla@jessica.w3.org
- [Bug 10265] New: Should this be "conversation"? bugzilla@jessica.w3.org
- [Bug 10255] address element needs to apply more granularly bugzilla@jessica.w3.org
- [Bug 10264] New: This paragraph is phrased awkwardly bugzilla@jessica.w3.org
- [Bug 9897] need closing quote and /> for the very last p tag bugzilla@jessica.w3.org
- [Bug 10263] New: Should there be functions available to add and remove resources to/from the cache using JavaScript? bugzilla@jessica.w3.org
- [Bug 10262] New: autocomplete attribute seams to do more than it should. There should be a 'confidential' attribute that will do all that is mention here and autocomplete=off would only disable autocomplete, but let browsers remember the value for back button. bugzilla@jessica.w3.org
- [Bug 10257] Meta charset sniffing need to resolve aliases before checking UTF-16ness bugzilla@jessica.w3.org
- [Bug 10257] Meta charset sniffing need to resolve aliases before checking UTF-16ness bugzilla@jessica.w3.org
- [Bug 10256] 3.2.2 Elements in the DOM bugzilla@jessica.w3.org
- [Bug 10252] HTML5 hard-binds "Action" to accesskey key-press bugzilla@jessica.w3.org
- [Bug 10251] Psuedo-Cascade of Multiple Accesskeys Definable for an Individual Element bugzilla@jessica.w3.org
- [Bug 10260] New: Meta charset handling during the parse should special-case UTF-16 and reject non-ASCII supersets bugzilla@jessica.w3.org
- [Bug 10257] Meta charset sniffing need to resolve aliases before checking UTF-16ness bugzilla@jessica.w3.org
- [Bug 10259] New: Make it clearer that <dt> can be used for questions and <dd> for answers (maybe move away from the terminology "name-value group"?) bugzilla@jessica.w3.org
- [Bug 10258] New: Spec should be more careful about UTF-16, UTF-16BE and UTF-16LE bugzilla@jessica.w3.org
- [Bug 10257] New: Meta charset sniffing need to resolve aliases before checking UTF-16ness bugzilla@jessica.w3.org
- [Bug 10256] New: 3.2.2 Elements in the DOM bugzilla@jessica.w3.org
- [Bug 10254] Missing word in "The address element" section bugzilla@jessica.w3.org
- [Bug 10255] address element needs to apply more granularly bugzilla@jessica.w3.org
- [Bug 10255] New: The earlier version where it said "If an address element applies to a section of a document, then it represents contact information for that section only" was a better approach. I see what you're after here, but it's way too 1996. "A web page" or "a docu bugzilla@jessica.w3.org
- [Bug 10254] New: Missing word in this sentence: "The contact information of node is the same as the contact information the body element of the Document." bugzilla@jessica.w3.org
- [Bug 10253] New: doesn't say anything except what the container type is, and even a type like bugzilla@jessica.w3.org
Wednesday, 28 July 2010
- [Bug 10252] New: HTML5 hard-binds "Action" to accesskey key-press bugzilla@jessica.w3.org
- [Bug 10251] New: Psuedo-Cascade of Multiple Accesskeys Definable for an Individual Element bugzilla@jessica.w3.org
- [Bug 10250] New: why must context menus not reflect changes in the DOM? Maybe some browsers want to always show the possible actions for an element. In order to do this they would have to regularly fire the contextmenu event to update it reflecting changes in the DOM. bugzilla@jessica.w3.org
- [Bug 10249] Canvas requires a content selection method bugzilla@jessica.w3.org
- [Bug 10248] Canvas requires a Caret Drawing call method bugzilla@jessica.w3.org
- [Bug 10249] Canvas requires a content selection method bugzilla@jessica.w3.org
- [Bug 10249] New: Canvas requires a content selection method bugzilla@jessica.w3.org
- [Bug 10248] New: Canvas requires a Caret Drawing call method bugzilla@jessica.w3.org
- [Bug 9969] The polyglot publication implies it is normative bugzilla@jessica.w3.org
- [Bug 10247] New: What should happen when the URL to be fetched is a mailto: URL or some other weird scheme. (Mostly curious in relation to EventSource, but it applies elsewhere too.) bugzilla@jessica.w3.org
- [Bug 10167] HTML5 Polyglot spec breaks RDFa case sensitivity bugzilla@jessica.w3.org
- [Bug 10246] Add "/* case-insensitive */" marker to selectors for [type=disc], [type=circle] and [type=square] bugzilla@jessica.w3.org
- [Bug 10246] New: Add "/* case-insensitive */" marker to selectors for [type=disc], [type=circle] and [type=square] bugzilla@jessica.w3.org
- [Bug 10245] Specify the exception that the case-insensitivity of the type attribute does not apply to the type attribute on ol elements bugzilla@jessica.w3.org
- [Bug 10245] New: Specify the exception that the case-insensitivity of the type attribute does not apply to the type attribute on ol elements bugzilla@jessica.w3.org
- [Bug 10066] replace section 3.2.6 with the alternative spec text provided bugzilla@jessica.w3.org
- [Bug 10066] replace section 3.2.6 with the alternative spec text provided bugzilla@jessica.w3.org
- [Bug 10066] replace section 3.2.6 with the alternative spec text provided bugzilla@jessica.w3.org
- [Bug 10066] replace section 3.2.6 with the alternative spec text provided bugzilla@jessica.w3.org
- [Bug 10066] replace section 3.2.6 with the alternative spec text provided bugzilla@jessica.w3.org
- [Bug 10066] replace section 3.2.6 with the alternative spec text provided bugzilla@jessica.w3.org
- [Bug 10066] replace section 3.2.6 with the alternative spec text provided bugzilla@jessica.w3.org
- [Bug 10244] The processing is not defined if the <ruby> content model is violated (e.g. if there are multiple <rt> elements, more than 2 <rp> elements, mis-ordered <rp> elements, and so forth. bugzilla@jessica.w3.org
- [Bug 10244] New: The processing is not defined if the <ruby> content model is violated (e.g. if there are multiple <rt> elements, more than 2 <rp> elements, mis-ordered <rp> elements, and so forth. bugzilla@jessica.w3.org
- [Bug 10066] replace section 3.2.6 with the alternative spec text provided bugzilla@jessica.w3.org
- [Bug 10066] replace section 3.2.6 with the alternative spec text provided bugzilla@jessica.w3.org
- [Bug 10066] replace section 3.2.6 with the alternative spec text provided bugzilla@jessica.w3.org
- [Bug 10066] replace section 3.2.6 with the alternative spec text provided bugzilla@jessica.w3.org
- [Bug 10066] replace section 3.2.6 with the alternative spec text provided bugzilla@jessica.w3.org
- [Bug 9187] Need transparency in issue and bug status in databases & document. bugzilla@jessica.w3.org
- [Bug 8893] Clarify how Change Proposals get reviewed and what happens to Change Proposals that do not meet requirements bugzilla@jessica.w3.org
- [Bug 9284] Consider giving guidelines for use of different bug resolutions bugzilla@jessica.w3.org
- [Bug 9284] Consider giving guidelines for use of different bug resolutions bugzilla@jessica.w3.org
- [Bug 8895] Document policy for First Public Working Drafts bugzilla@jessica.w3.org
- [Bug 9918] Consider adding a consensus-building component into the decision process bugzilla@jessica.w3.org
- [Bug 10084] Please consider adding a section on Chair recusal in deciding escalated issues bugzilla@jessica.w3.org
- [Bug 9901] co-chairs should also address objections raised in change proposals bugzilla@jessica.w3.org
- [Bug 8894] Document process for counter-proposals and alternate proposals bugzilla@jessica.w3.org
- [Bug 9898] The Decision Policy (as applied) is ineffective at getting closure on ISSUEs bugzilla@jessica.w3.org
- [Bug 9894] The chairs should be required to ensure that decisions result in consistent specifications bugzilla@jessica.w3.org
- [Bug 9894] The chairs should be required to ensure that decisions result in consistent specifications bugzilla@jessica.w3.org
- [Bug 8895] Document policy for First Public Working Drafts bugzilla@jessica.w3.org
- [Bug 9792] Clarify that no-change counter-proposals need to document rationale for the existing text bugzilla@jessica.w3.org
- [Bug 8894] Document process for counter-proposals and alternate proposals bugzilla@jessica.w3.org
- [Bug 8891] No change or so-called zero edit proposals bugzilla@jessica.w3.org
- [Bug 8891] No change or so-called zero edit proposals bugzilla@jessica.w3.org
- [Bug 10243] New: It should register Refresh: HTTP header field, as wiki-registered pragma extensions are forced to do bugzilla@jessica.w3.org
Tuesday, 27 July 2010
- [Bug 9574] Floating point number tolerance bugzilla@jessica.w3.org
- [Bug 7237] Let current outlinee be null. (It holds the element whose outline is being created.) Spelling. Outline with one "e" bugzilla@jessica.w3.org
- [Bug 10201] typo: "1. Let current outlinee" bugzilla@jessica.w3.org
- [Bug 10241] New: The platform specific activation behavior does not work in practice. E.g. http://us.starcraft2.com/dominion/entrance-exam-qna.xml relies on a click event for a display:none input element. The Web is the platform so we should just standardize on that :-) bugzilla@jessica.w3.org
- [Bug 10239] How about using file-extensions instead of mime-types? It would allow application-specific files to be set as allowed. bugzilla@jessica.w3.org
- [Bug 10239] How about using file-extensions instead of mime-types? It would allow application-specific files to be set as allowed. bugzilla@jessica.w3.org
- [Bug 10240] Just setting the <script> to "already started" doesn't prevent it from running if we then immediately "run" it. bugzilla@jessica.w3.org
- [Bug 10240] Just setting the <script> to "already started" doesn't prevent it from running if we then immediately "run" it. bugzilla@jessica.w3.org
- [Bug 10240] New: Just setting the <script> to "already started" doesn't prevent it from running if we then immediately "run" it. bugzilla@jessica.w3.org
Monday, 26 July 2010
- [Bug 10239] New: How about using file-extensions instead of mime-types? It would allow application-specific files to be set as allowed. bugzilla@jessica.w3.org
- [Bug 8833] Please allow the title of the spec currently known as "HTML5" to be changed to an accurate title. bugzilla@jessica.w3.org
- [Bug 8834] Please remove the subtitle from the spec known as "HTML5" bugzilla@jessica.w3.org
- [Bug 10232] There is no "|selected| attribute is a boolean attribute" bugzilla@jessica.w3.org
- [Bug 10237] hi hello how are you bugzilla@jessica.w3.org
- [Bug 10237] New: hi hello how are you bugzilla@jessica.w3.org
Saturday, 24 July 2010
- [Bug 10232] New: There is no "|selected| attribute is a boolean attribute" bugzilla@jessica.w3.org
- [Bug 9919] Remove kbd, samp, and maybe var, like acronym; expand <code>/<tt>/<i> or whatever to replace them bugzilla@jessica.w3.org
Friday, 23 July 2010
- [Bug 9919] Remove kbd, samp, and maybe var, like acronym; expand <code>/<tt>/<i> or whatever to replace them bugzilla@jessica.w3.org
- [Bug 9919] Remove kbd, samp, and maybe var, like acronym; expand <code>/<tt>/<i> or whatever to replace them bugzilla@jessica.w3.org
- [Bug 9824] comentariu destul de mare pentru ca editorul sa il inteleeaga bugzilla@jessica.w3.org
- [Bug 10231] New: When a track element is created, it must be associated with a new timed track (with its value set as defined below) and its corresponding new TimedTrack object. bugzilla@jessica.w3.org
- [Bug 10230] Decisions need to be made in timely manner bugzilla@jessica.w3.org
- [Bug 10230] New: Decisions need to be made in timely manner bugzilla@jessica.w3.org
- [Bug 10084] Please consider adding a section on Chair recusal in deciding escalated issues bugzilla@jessica.w3.org
- [Bug 10224] please add IDs to each attribute row in "List of event handler content attributes" table bugzilla@jessica.w3.org
- [Bug 10224] please add IDs to each attribute row in "List of event handler content attributes" table bugzilla@jessica.w3.org
- [Bug 10224] please add IDs to each attribute row in "List of event handler content attributes" table bugzilla@jessica.w3.org
- [Bug 10224] please add IDs to each attribute row in "List of event handler content attributes" table bugzilla@jessica.w3.org
- [Bug 10224] please add IDs to each attribute row in "List of event handler content attributes" table bugzilla@jessica.w3.org
- [Bug 10224] please add IDs to each attribute row in "List of event handler content attributes" table bugzilla@jessica.w3.org
- [Bug 10197] xml:space is not listed as a global attribute bugzilla@jessica.w3.org
- [Bug 9919] samp and kbd are practically unused and just clutter the language. They should be removed, like acronym, and code should be broadened to include their semantics (or maybe tt should be re-permitted and defined in the fashion of b and i). bugzilla@jessica.w3.org
- [Bug 10229] New: "for timed tracks whose kind is chapters, the user agent is making available to the user a mechanism by which the user can navigate to any point in the media resource by selecting a cue" says the spec, but how is not actually defined anywhere bugzilla@jessica.w3.org
Thursday, 22 July 2010
- [Bug 10228] write-neutralized is a horrible, horrible name bugzilla@jessica.w3.org
- [Bug 10228] New: write-neutralized is a horrible, horrible name bugzilla@jessica.w3.org
- [Bug 10227] New: It'd be nice to have a collected IDL in an appendix. bugzilla@jessica.w3.org
- [Bug 10226] New: Typo: "Updates the current entry in the session histor to have..." s/histor/history/ --@miketaylr bugzilla@jessica.w3.org
- [Bug 10221] Always coalesce adjacent text nodes even in the case where the previous node was not the one last inserted by the parser. bugzilla@jessica.w3.org
- [Bug 10225] New: ugly prefix "href", why not use the lang directly? bugzilla@jessica.w3.org
- [Bug 10224] New: please add IDs to each attribute row in "List of event handler content attributes" table bugzilla@jessica.w3.org
Wednesday, 21 July 2010
- [Bug 10223] Presumably button shouldn't appear in this list given that we have a notion of "in button scope" which explicitly adds button to this list... bugzilla@jessica.w3.org
- [Bug 10223] New: Presumably button shouldn't appear in this list given that we have a notion of "in button scope" which explicitly adds button to this list... bugzilla@jessica.w3.org
- [Bug 10222] button appears twice in the list of special elements bugzilla@jessica.w3.org
- [Bug 10222] New: button appears twice in the list of special elements bugzilla@jessica.w3.org
- [Bug 10221] Always coalesce adjacent text nodes even in the case where the previous node was not the one last inserted by the parser. bugzilla@jessica.w3.org
- [Bug 10221] New: Always coalesce adjacent text nodes even in the case where the previous node was not the one last inserted by the parser. bugzilla@jessica.w3.org
- [Bug 10177] Typo in 'An end tag whose tag name is "p"': "sbutton cope" bugzilla@jessica.w3.org
- [Bug 10219] "in sbutton cope" bugzilla@jessica.w3.org
- [Bug 10220] New: button already is in the elements listed above, so "in button scope" is the same as "in scope" bugzilla@jessica.w3.org
- [Bug 10219] New: "in sbutton cope" bugzilla@jessica.w3.org
- [Bug 8966] Consider "<svg><desc><div><svg><desc><b>X" â Should we change "Pop elements from the stack of open elements until the current node is in the HTML namespace." in the in-foreign-content mode to actually be "Pop elements until there's no element in scope t bugzilla@jessica.w3.org
- [Bug 10160] Jack Bauerâs name is a poor example of using meta, as the content is already present bugzilla@jessica.w3.org
- [Bug 10217] New: EOF after foreign content can cause crash bugzilla@jessica.w3.org
- [Bug 10216] When inserting a <form> element in table we need to set the form element pointer to point to the element created. bugzilla@jessica.w3.org
- [Bug 10216] When inserting a <form> element in table we need to set the form element pointer to point to the element created. bugzilla@jessica.w3.org
- [Bug 10216] New: When inserting a <form> element in table we need to set the form element pointer to point to the element created. bugzilla@jessica.w3.org
- [Bug 10215] New: not sure what's mean by "User agents must _synchronously_ run the focusing steps". Does this mean that the event handlers involved in steps 1 and and 3 must return before further steps in the procedure can be taken? A reasonable alternative interpretation bugzilla@jessica.w3.org
- [Bug 8118] Remove the Hidden Attribute bugzilla@jessica.w3.org
- [Bug 10066] replace section 3.2.6 with the alternative spec text provided bugzilla@jessica.w3.org
Tuesday, 20 July 2010
- [Bug 10214] New: In the "lighter" operator, it says "with color values approaching 1 as a limit". You mean "approaching 255" - color values are octets, not floats in [0,1]. bugzilla@jessica.w3.org
- [Bug 10213] The definition of "absolute url" makes https:foo not an absolute url, since its behavior depends on whether the base is https: or not. Is that desired? In particular, using this definition for websockets means that wss: urls with no forward slashes afte bugzilla@jessica.w3.org
- [Bug 10213] New: The definition of "absolute url" makes https:foo not an absolute url, since its behavior depends on whether the base is https: or not. Is that desired? In particular, using this definition for websockets means that wss: urls with no forward slashes afte bugzilla@jessica.w3.org
- [Bug 10212] New: Redundant? This is implied by the heading. bugzilla@jessica.w3.org
- [Bug 10210] New: I prefer to have some legacy content show up faulty than to introduce an artificial complexity for the generations to come bugzilla@jessica.w3.org
- [Bug 10206] New: A single manifest file pre page will be problematic for web authoring programmers like myself, and Lib developers like jQuery. It will cause all types of problems with mash-ups of various providers of web apps on a single page. Can U please consider addin bugzilla@jessica.w3.org
Monday, 19 July 2010
- [Bug 10204] The algorithm is unclear here whether we mean the "current node" at this point in time or the "current node" at the time the insertion occurs (which might be different). As an example, consider "<table><p><p>Foo". I think you mean the current element at bugzilla@jessica.w3.org
- [Bug 10204] New: The algorithm is unclear here whether we mean the "current node" at this point in time or the "current node" at the time the insertion occurs (which might be different). As an example, consider "<table><p><p>Foo". I think you mean the current element at bugzilla@jessica.w3.org
- [Bug 10202] New: use of "codecs" parameter bugzilla@jessica.w3.org
- [Bug 10201] New: typo: "1. Let current outlinee" bugzilla@jessica.w3.org
- [Bug 10200] just a test bugzilla@jessica.w3.org
- [Bug 10200] New: just a test bugzilla@jessica.w3.org
- [Bug 10196] Relationship to xml:id bugzilla@jessica.w3.org
- [Bug 10160] Jack Bauerâs name is a poor example of using meta, as the content is already present bugzilla@jessica.w3.org
- [Bug 10159] For vCard, itemprop="fn" and itemprop="n" can be combined bugzilla@jessica.w3.org
- [Bug 10199] Some vcard examples lack itemscope on itemprop="n" elements bugzilla@jessica.w3.org
- [Bug 10199] New: Some vcard examples lack itemscope on itemprop="n" elements bugzilla@jessica.w3.org
Sunday, 18 July 2010
- [Bug 10159] For vCard, itemprop="fn" and itemprop="n" can be combined bugzilla@jessica.w3.org
- [Bug 10196] Relationship to xml:id bugzilla@jessica.w3.org
- [Bug 10196] Relationship to xml:id bugzilla@jessica.w3.org
- [Bug 10198] New: The Gregorian is not a Universal standard for calendars. HTML5 must provide ways for other calendar types. e.g. The "Hijri" calendar is used throughout in Arab countries. The "Persian" calendar is used in Iran, Afghanistan and Pakistan. The "Hebrew" calen bugzilla@jessica.w3.org
- [Bug 10197] New: xml:space is not listed as a global attribute bugzilla@jessica.w3.org
- [Bug 10196] Relationship to xml:id bugzilla@jessica.w3.org
- [Bug 10196] New: Relationship to xml:id bugzilla@jessica.w3.org
Saturday, 17 July 2010
- [Bug 10195] New: length function does not work for SVG circle and line elements bugzilla@jessica.w3.org
- [Bug 10194] New: "If the first argument to the method is null or not an ImageData object then the putImageData() method must raise a TYPE_MISMATCH_ERR exception." - it can be null but never not an ImageData (because WebIDL should enforce that) bugzilla@jessica.w3.org
- [Bug 10193] New: "If any of the arguments to the method are infinite or NaN, the method must raise a NOT_SUPPORTED_ERR exception." - this is redundant, since the spec earlier says "Except where otherwise specified, if a method with an argument that is a floating point num bugzilla@jessica.w3.org
- [Bug 10192] New: item() should return Element, unlike namedItem bugzilla@jessica.w3.org
- [Bug 8550] Add document.createElement("<div>") (Gecko quirks, IE)? [ms] bugzilla@jessica.w3.org
- [Bug 10188] i just demo bugzilla@jessica.w3.org
- [Bug 10189] i just demo bugzilla@jessica.w3.org
- [Bug 10190] i just demo bugzilla@jessica.w3.org
- [Bug 10191] how to use bugzilla@jessica.w3.org
- [Bug 10191] New: how to use bugzilla@jessica.w3.org
- [Bug 10190] New: i just demo bugzilla@jessica.w3.org
- [Bug 10189] New: i just demo bugzilla@jessica.w3.org
- [Bug 10188] New: i just demo bugzilla@jessica.w3.org
Friday, 16 July 2010
- [Bug 10187] New: Should say "...objects that browsing context..." bugzilla@jessica.w3.org
- [Bug 10186] New: typo: e.g. because it a simple movie file - s/it a/it is a/ bugzilla@jessica.w3.org
- [Bug 9966] Include a history section. Say that this spec replaces Appendix C and related docs bugzilla@jessica.w3.org
- [Bug 10185] New: I would like to suggest that "4.8.1.1.9 A Key Part of the content" is moved up, so it becomes 4.8.1.1.1 i.e. it is the first subsection. This subsection seems to be the most important or dominant case, whereas the others are important, but are exceptions? bugzilla@jessica.w3.org
- [Bug 9767] Consider ignoring document.write() when IE ignores it if comes from the network task source bugzilla@jessica.w3.org
- [Bug 10184] Please spec HTMLOptionsCollection.selectedIndex bugzilla@jessica.w3.org
- [Bug 10184] New: Please spec HTMLOptionsCollection.selectedIndex bugzilla@jessica.w3.org
- [Bug 10084] Please consider adding a section on Chair recusal in deciding escalated issues bugzilla@jessica.w3.org
- [Bug 10084] Please consider adding a section on Chair recusal in deciding escalated issues bugzilla@jessica.w3.org
- [Bug 10183] New: "then the WebSRT file must WebSRT file using cue text.": Fix grammar bugzilla@jessica.w3.org
- [Bug 10181] its not valid according to newer version of xhtml bugzilla@jessica.w3.org
- [Bug 9767] Consider ignoring document.write() when IE ignores it if comes from the network task source bugzilla@jessica.w3.org
- [Bug 10181] New: its not valid according to newer version of xhtml bugzilla@jessica.w3.org
- [Bug 10179] New: Add example of addTrack() for the purposes of scripted pausing of the video. (i.e. the old cue range use case) bugzilla@jessica.w3.org
Thursday, 15 July 2010
- [Bug 9767] Consider ignoring document.write() when IE ignores it if comes from the network task source bugzilla@jessica.w3.org
- [Bug 10178] New: In the DOM tree visualisation the doctype node is presented weird: The string "html" is marked up like a reference to the definition of the HTML element; like it is done with all following nodes. That just leads to a doubled link to the HTML element defin bugzilla@jessica.w3.org
- [Bug 9673] Remove any reference to a specific Time Stamp format for video captioning from the specification at this time bugzilla@jessica.w3.org
- [Bug 10177] New: Typo in 'An end tag whose tag name is "p"': "sbutton cope" bugzilla@jessica.w3.org
- [Bug 10083] Remove references to Microdata from within the document bugzilla@jessica.w3.org
- [Bug 10083] Remove references to Microdata from within the document bugzilla@jessica.w3.org
- [Bug 10117] Tag name state algorithm has mis-ordered step bugzilla@jessica.w3.org
- [Bug 10173] New: Foreign Content bugzilla@jessica.w3.org
- [Bug 9984] [parser] Insertion point for script@onload doesn't match Firefox bugzilla@jessica.w3.org
- [Bug 9767] Consider ignoring document.write() when IE ignores it if comes from the network task source bugzilla@jessica.w3.org
- [Bug 10172] New: nofollow/noreferrer not allowed on <link> bugzilla@jessica.w3.org
- [Bug 10171] New: Button is in the list twice bugzilla@jessica.w3.org
- [Bug 10170] New: I really think it should be possible to nest the ul and ol elements using normal tag standard. whey not make it possible to nest it by allowing ul/ol inside other ul/ol tags, just like any other li elements? bugzilla@jessica.w3.org
- [Bug 10169] The discontinuity at shadowBlur = 8 here is weird. We have no interop on exact shadow algorithms right now anyway, so maybe it could be fixed in the spec? Clearly authors aren't depending on pixel-perfect canvas shadows. Maybe it should just be the num bugzilla@jessica.w3.org
- [Bug 9771] It's slightly strange that the Tokenizer keeps changing the "insertion mode" which appears to be parser-state. eric@webkit.org bugzilla@jessica.w3.org
Wednesday, 14 July 2010
- [Bug 10169] The discontinuity at shadowBlur = 8 here is weird. We have no interop on exact shadow algorithms right now anyway, so maybe it could be fixed in the spec? Clearly authors aren't depending on pixel-perfect canvas shadows. Maybe it should just be the num bugzilla@jessica.w3.org
- [Bug 9984] [parser] Insertion point for script@onload doesn't match Firefox bugzilla@jessica.w3.org
- [Bug 10093] Typo: "either the element's end tag is parsed on the parser detects" should be "is parsed _or_ the parser detects" bugzilla@jessica.w3.org
- [Bug 10158] HTML5 parser: comments after </body> and after </html> should be put in body bugzilla@jessica.w3.org
- [Bug 10093] Typo: "either the element's end tag is parsed on the parser detects" should be "is parsed _or_ the parser detects" bugzilla@jessica.w3.org
- [Bug 9771] It's slightly strange that the Tokenizer keeps changing the "insertion mode" which appears to be parser-state. eric@webkit.org bugzilla@jessica.w3.org
- [Bug 9535] Consider the poem example of figure. It should be possible to omit the </p> tag there. Maybe we should make <figcaption> imply </p> in the parser. bugzilla@jessica.w3.org
- [Bug 9535] Consider the poem example of figure. It should be possible to omit the </p> tag there. Maybe we should make <figcaption> imply </p> in the parser. bugzilla@jessica.w3.org
- [Bug 10158] HTML5 parser: comments after </body> and after </html> should be put in body bugzilla@jessica.w3.org
- [Bug 9843] Specced behavior for document.write("<link rel=stylesheet href=...><script>...</script>...") matches none of the top 4 engines bugzilla@jessica.w3.org
- [Bug 10157] Whitespace between <head> and <body> should be ignored bugzilla@jessica.w3.org
- [Bug 10140] Not possible to ever leave "secondary insertion mode" bugzilla@jessica.w3.org
- [Bug 10169] The discontinuity at shadowBlur = 8 here is weird. We have no interop on exact shadow algorithms right now anyway, so maybe it could be fixed in the spec? Clearly authors aren't depending on pixel-perfect canvas shadows. Maybe it should just be the num bugzilla@jessica.w3.org
- [Bug 10117] Tag name state algorithm has mis-ordered step bugzilla@jessica.w3.org
- [Bug 10117] Tag name state algorithm has mis-ordered step bugzilla@jessica.w3.org
- [Bug 10169] The discontinuity at shadowBlur = 8 here is weird. We have no interop on exact shadow algorithms right now anyway, so maybe it could be fixed in the spec? Clearly authors aren't depending on pixel-perfect canvas shadows. Maybe it should just be the num bugzilla@jessica.w3.org
- [Bug 10169] New: The discontinuity at shadowBlur = 8 here is weird. We have no interop on exact shadow algorithms right now anyway, so maybe it could be fixed in the spec? Clearly authors aren't depending on pixel-perfect canvas shadows. Maybe it should just be the num bugzilla@jessica.w3.org
- [Bug 10096] Adoption Agency 6.4 and 6.5 should be re-ordered bugzilla@jessica.w3.org
- [Bug 10098] Stray comma or typo in "in cell" "end tag whos name is 'table'" case bugzilla@jessica.w3.org
- [Bug 10096] Adoption Agency 6.4 and 6.5 should be re-ordered bugzilla@jessica.w3.org
- [Bug 10080] "in body" insertion mode, "any other end tag", step 2.2 seems wrong. bugzilla@jessica.w3.org
- [Bug 10080] "in body" insertion mode, "any other end tag", step 2.2 seems wrong. bugzilla@jessica.w3.org
- [Bug 10063] Foster Parenting Paragraph is confusing bugzilla@jessica.w3.org
- [Bug 10080] "in body" insertion mode, "any other end tag", step 2.2 seems wrong. bugzilla@jessica.w3.org
- [Bug 10063] Foster Parenting Paragraph is confusing bugzilla@jessica.w3.org
- [Bug 10055] </html> and </body> in "in foreign content" cause severe badness bugzilla@jessica.w3.org
- [Bug 9984] [parser] Insertion point for script@onload doesn't match Firefox bugzilla@jessica.w3.org
- [Bug 9985] [parser] How to parse </foo </bar> bugzilla@jessica.w3.org
- [Bug 9984] [parser] Insertion point for script@onload doesn't match Firefox bugzilla@jessica.w3.org
- [Bug 9910] <basefont> and <bgsound> should not break out of 'in head', should be treated as a void elements within <head> bugzilla@jessica.w3.org
- [Bug 9910] <basefont> and <bgsound> should not break out of 'in head', should be treated as a void elements within <head> bugzilla@jessica.w3.org
- [Bug 9831] Handling of EOF in foreignContent mode causes all tags to be popped of stack of open elements bugzilla@jessica.w3.org
- [Bug 9831] Handling of EOF in foreignContent mode causes all tags to be popped of stack of open elements bugzilla@jessica.w3.org
- [Bug 9829] <button> should be scoping for the purpose of implicitly closing <p> bugzilla@jessica.w3.org
- [Bug 9829] <button> should be scoping for the purpose of implicitly closing <p> bugzilla@jessica.w3.org
- [Bug 10168] New: Please consider adding a section on role="presentation" bugzilla@jessica.w3.org
- [Bug 9767] Consider ignoring document.write() when IE ignores it if comes from the network task source bugzilla@jessica.w3.org
- [Bug 10167] HTML5 Polyglot spec breaks RDFa case sensitivity bugzilla@jessica.w3.org
- [Bug 10167] New: HTML5 Polyglot spec breaks RDFa case sensitivity bugzilla@jessica.w3.org
- [Bug 10166] New: Where is the <datagrid>? bugzilla@jessica.w3.org
- [Bug 10164] Get rid of RadioNodeList bugzilla@jessica.w3.org
- [Bug 10164] New: Get rid of RadioNodeList bugzilla@jessica.w3.org
- [Bug 10161] Mention <meta content=""> specifically in Microdataâs basic syntax bugzilla@jessica.w3.org
- [Bug 10161] New: Mention <meta content=""> specifically in Microdataâs basic syntax bugzilla@jessica.w3.org
- [Bug 10160] Jack Bauerâs name is a poor example of using meta, as the content is already present bugzilla@jessica.w3.org
- [Bug 10160] New: Jack Bauerâs name is a poor example of using meta, as the content is already present bugzilla@jessica.w3.org
- [Bug 10159] For vCard, itemprop="fn" and itemprop="n" can be combined bugzilla@jessica.w3.org
- [Bug 10159] New: For vCard, itemprop="fn" and itemprop="n" can be combined bugzilla@jessica.w3.org
- [Bug 9829] <button> should be scoping for the purpose of implicitly closing <p> bugzilla@jessica.w3.org
- [Bug 9767] Consider ignoring document.write() when IE ignores it if comes from the network task source bugzilla@jessica.w3.org
- [Bug 9767] Consider ignoring document.write() when IE ignores it if comes from the network task source bugzilla@jessica.w3.org
- [Bug 9659] Initial U+0000 should not set frameset-ok to "not ok" bugzilla@jessica.w3.org
- [Bug 9659] Initial U+0000 should not set frameset-ok to "not ok" bugzilla@jessica.w3.org
- [Bug 9582] Steps for handling end tags in the "in foreign" mode get stuck in an infinite loop bugzilla@jessica.w3.org
- [Bug 9581] Steps for handling end tags in the "in foreign" mode may compare the name of an already-popped node bugzilla@jessica.w3.org
- [Bug 9580] Steps for handling end tags in the "in foreign" mode walk past the root node in the stack bugzilla@jessica.w3.org
- [Bug 9580] Steps for handling end tags in the "in foreign" mode walk past the root node in the stack bugzilla@jessica.w3.org
- [Bug 9673] Remove any reference to a specific Time Stamp format for video captioning from the specification at this time bugzilla@jessica.w3.org
Tuesday, 13 July 2010
- [Bug 10158] New: HTML5 parser: comments after </body> and after </html> should be put in body bugzilla@jessica.w3.org
- [Bug 10139] active form element markers are never removed bugzilla@jessica.w3.org
- [Bug 10157] New: Whitespace between <head> and <body> should be ignored bugzilla@jessica.w3.org
- [Bug 10156] New: [polyglot] i18n comment 3 : BOM with utf-8 and/or utf-16 bugzilla@jessica.w3.org
- [Bug 10155] New: [polyglot] i18n comment 8 : ployglot bugzilla@jessica.w3.org
- [Bug 10154] New: [polyglot] i18n comment 7 : Named entity references bugzilla@jessica.w3.org
- [Bug 10153] New: [polyglot] i18n comment 6 : Case requirements bugzilla@jessica.w3.org
- [Bug 10152] New: [polyglot] i18n comment 5 : Mention lang and xml:lang bugzilla@jessica.w3.org
- [Bug 10151] New: [polyglot] i18n comment 4 : Omit the either/or list bugzilla@jessica.w3.org
- [Bug 10150] New: [polyglot] i18n comment 2 : In-document declarations always useful bugzilla@jessica.w3.org
- [Bug 10149] New: [polyglot] i18n comment 1 : UTF-16 BOM is required bugzilla@jessica.w3.org
- [Bug 10141] itemscope is long and not very descriptive. how about just scope and prop. bugzilla@jessica.w3.org
- [Bug 10148] New: allow a BOM bugzilla@jessica.w3.org
- [Bug 10147] Allow td in thead bugzilla@jessica.w3.org
- [Bug 10147] New: Allow td in thead bugzilla@jessica.w3.org
- [Bug 10145] lop lop lop lop loplop bugzilla@jessica.w3.org
- [Bug 10136] I would love some clarification about the DOM tree example. Why is there no text node between DOCTYPE and <html>? Between <html> and <head>? Two at the end of <body>? I'm very picky :-) bugzilla@jessica.w3.org
- [Bug 10146] New: Labelability of hidden form inputs unclear bugzilla@jessica.w3.org
- [Bug 10145] New: lop lop lop lop loplop bugzilla@jessica.w3.org
- [Bug 10083] Remove references to Microdata from within the document bugzilla@jessica.w3.org
- [Bug 10141] New: itemscope is long and not very descriptive. how about just scope and prop. bugzilla@jessica.w3.org
- [Bug 10139] active form element markers are never removed bugzilla@jessica.w3.org
- [Bug 10140] Not possible to ever leave "secondary insertion mode" bugzilla@jessica.w3.org
- [Bug 10140] New: Not possible to ever leave "secondary insertion mode" bugzilla@jessica.w3.org
- [Bug 10139] active form element markers are never removed bugzilla@jessica.w3.org
- [Bug 10139] New: active form element markers are never removed bugzilla@jessica.w3.org
- [Bug 9767] Consider ignoring document.write() when IE ignores it if comes from the network task source bugzilla@jessica.w3.org
Monday, 12 July 2010
- [Bug 10138] New: The rs232 option should be kept so that physical web devices like an Arduino can be programmed to interact with a web page to enable physical web interfaces. bugzilla@jessica.w3.org
- [Bug 10083] Remove references to Microdata from within the document bugzilla@jessica.w3.org
- [Bug 10137] New: What criteria should browsers use to determine whether a URL's hash fragment differs from the previous one? Should the comparison be case-sensitive? Currently, all implementations of hashchange use case-sensitive comparisons except IE8, which uses a case- bugzilla@jessica.w3.org
- [Bug 10136] New: I would love some clarification about the DOM tree example. Why is there no text node between DOCTYPE and <html>? Between <html> and <head>? Two at the end of <body>? I'm very picky :-) bugzilla@jessica.w3.org
- [Bug 10117] Tag name state algorithm has mis-ordered step bugzilla@jessica.w3.org
- [Bug 9958] The DOCTYPE paragraph must explain and define the DOCTYPE rules better and more generally bugzilla@jessica.w3.org
Sunday, 11 July 2010
- [Bug 9767] Consider ignoring document.write() when IE ignores it if comes from the network task source bugzilla@jessica.w3.org
- [Bug 10133] New: Use of this element requires passing a contextID string to getContext, but the standard does prescribe either (a) an enumeration of valid contextIDs or (b) a method to enumerat the contextIDs supported by a given UA. (b) should be a requirement of the sta bugzilla@jessica.w3.org
- [Bug 10132] New: A CanvasPattern object should have a way to offset the repitition of an image. bugzilla@jessica.w3.org
- [Bug 9670] Allow "size" attribute for input-type "number" bugzilla@jessica.w3.org
Saturday, 10 July 2010
- [Bug 9767] Consider ignoring document.write() when IE ignores it if comes from the network task source bugzilla@jessica.w3.org
- [Bug 9767] Consider ignoring document.write() when IE ignores it if comes from the network task source bugzilla@jessica.w3.org
- [Bug 9767] Consider ignoring document.write() when IE ignores it if comes from the network task source bugzilla@jessica.w3.org
- [Bug 10126] The arc() function's last argument should be optional. Webkit doesn't require it, treating it as false if not provided. bugzilla@jessica.w3.org
- [Bug 10126] New: The arc() function's last argument should be optional. Webkit doesn't require it, treating it as false if not provided. bugzilla@jessica.w3.org
- [Bug 9958] The DOCTYPE paragraph must explain and define the DOCTYPE rules better and more generally bugzilla@jessica.w3.org
- [Bug 10014] XHTML1 Doctypes cause DOM diff in XML parsers with external entity handling bugzilla@jessica.w3.org
- [Bug 9972] colgroup not mentioned bugzilla@jessica.w3.org
- [Bug 9971] The XLink namespace is suggested to be declared on <html> bugzilla@jessica.w3.org
- [Bug 9971] The XLink namespace is suggested to be declared on <html> bugzilla@jessica.w3.org
- [Bug 9958] The DOCTYPE paragraph must explain and define the DOCTYPE rules better and more generally bugzilla@jessica.w3.org
- [Bug 10075] specify that polyglot docs do not contain xml:space or xml:base attributes bugzilla@jessica.w3.org
Friday, 9 July 2010
- [Bug 10075] specify that polyglot docs do not contain xml:space or xml:base attributes bugzilla@jessica.w3.org
- [Bug 9966] Include a history section. Say that this spec replaces Appendix C and related docs bugzilla@jessica.w3.org
- [Bug 9767] Consider ignoring document.write() when IE ignores it if comes from the network task source bugzilla@jessica.w3.org
- [Bug 9767] Consider ignoring document.write() when IE ignores it if comes from the network task source bugzilla@jessica.w3.org
- [Bug 10122] re: resolving a step mismatch, it would be good to state that if two values are equally near to round up bugzilla@jessica.w3.org
- [Bug 10122] re: resolving a step mismatch, it would be good to state that if two values are equally near to round up bugzilla@jessica.w3.org
- [Bug 10122] New: re: resolving a step mismatch, it would be good to state that if two values are equally near to round up bugzilla@jessica.w3.org
- [Bug 9831] Handling of EOF in foreignContent mode causes all tags to be popped of stack of open elements bugzilla@jessica.w3.org
- [Bug 10115] EOF handling in foreign content needs to change the insertion mode bugzilla@jessica.w3.org
- [Bug 10080] "in body" insertion mode, "any other end tag", step 2.2 seems wrong. bugzilla@jessica.w3.org
- [Bug 10078] Step 2.2 of "in body" "any other end tag" seems wrong. bugzilla@jessica.w3.org
- [Bug 10075] specify that polyglot docs do not contain xml:space or xml:base attributes bugzilla@jessica.w3.org
- [Bug 9961] View Source: Please base the markup of the polyglot spec on the polyglot spec bugzilla@jessica.w3.org
- [Bug 9580] Steps for handling end tags in the "in foreign" mode walk past the root node in the stack bugzilla@jessica.w3.org
- [Bug 10118] in foreign content "current node is not an element in the HTML namespace" algorithm is wrong bugzilla@jessica.w3.org
- [Bug 9831] Handling of EOF in foreignContent mode causes all tags to be popped of stack of open elements bugzilla@jessica.w3.org
- [Bug 9817] Details element Focus problem bugzilla@jessica.w3.org
- [Bug 10115] EOF handling in foreign content needs to change the insertion mode bugzilla@jessica.w3.org
- [Bug 9767] Consider ignoring document.write() when IE ignores it if comes from the network task source bugzilla@jessica.w3.org
- [Bug 10118] in foreign content "current node is not an element in the HTML namespace" algorithm is wrong bugzilla@jessica.w3.org
- [Bug 10118] New: in foreign content "current node is not an element in the HTML namespace" algorithm is wrong bugzilla@jessica.w3.org
- [Bug 10083] Remove references to Microdata from within the document bugzilla@jessica.w3.org
- [Bug 10117] Tag name state algorithm has mis-ordered step bugzilla@jessica.w3.org
- [Bug 10117] New: Tag name state algorithm has mis-ordered step bugzilla@jessica.w3.org
- [Bug 10116] New: HTMLFrameElement is missing contentWindow attribute bugzilla@jessica.w3.org
Thursday, 8 July 2010
- [Bug 10077] The <embed> should support an alt attribute. While the embedded content should provide for accessilibility of the embedded object, the developer doesn't always have control over those content, some embeddable formats are inherently less accessible, and th bugzilla@jessica.w3.org
- [Bug 10075] specify that polyglot docs do not contain xml:space or xml:base attributes bugzilla@jessica.w3.org
- [Bug 9968] The definition of 'polyglot document' should be be stricter bugzilla@jessica.w3.org
- [Bug 10014] XHTML1 Doctypes cause DOM diff in XML parsers with external entity handling bugzilla@jessica.w3.org
- [Bug 9969] The polyglot publication implies it is normative bugzilla@jessica.w3.org
- [Bug 9966] Include a history section. Say that this spec replaces Appendix C and related docs bugzilla@jessica.w3.org
- [Bug 9962] Permitted Character Encodings should be UTF-8 (recommended) and UTF-16 (permitted) bugzilla@jessica.w3.org
- [Bug 9961] View Source: Please base the markup of the polyglot spec on the polyglot spec bugzilla@jessica.w3.org
- [Bug 9958] The DOCTYPE paragraph must explain and define the DOCTYPE rules better and more generally bugzilla@jessica.w3.org
- [Bug 10115] EOF handling in foreign content needs to change the insertion mode bugzilla@jessica.w3.org
- [Bug 10115] EOF handling in foreign content needs to change the insertion mode bugzilla@jessica.w3.org
- [Bug 10115] EOF handling in foreign content needs to change the insertion mode bugzilla@jessica.w3.org
- [Bug 10115] EOF handling in foreign content needs to change the insertion mode bugzilla@jessica.w3.org
- [Bug 10115] New: EOF handling in foreign content needs to change the insertion mode bugzilla@jessica.w3.org
- [Bug 9971] The XLink namespace is suggested to be declared on <html> bugzilla@jessica.w3.org
- [Bug 9972] colgroup not mentioned bugzilla@jessica.w3.org
- [Bug 9685] empty elements in polyglot documents bugzilla@jessica.w3.org
- [Bug 10114] New: Rather than having inline documentation for external scripts, what would be infinitely more useful would be the contents of a script tag with a src attribute should be executed upon the complete loading and execution of the remote script. Therefore <scrip bugzilla@jessica.w3.org
- [Bug 9684] textarea and pre elements in polyglot document bugzilla@jessica.w3.org
- [Bug 9683] tbody element in Polyglot documents bugzilla@jessica.w3.org
- [Bug 10083] Remove references to Microdata from within the document bugzilla@jessica.w3.org
- [Bug 9959] Remove the wording"polyglot document" and incorporate formulations from title instead bugzilla@jessica.w3.org
- [Bug 10113] New: make </rt> optional (in syntax and parser) bugzilla@jessica.w3.org
- [Bug 10112] New: should element.click() also set focus on the clicked element? This is not clear from the steps given for the click() method bugzilla@jessica.w3.org
- [Bug 9122] Obsolete but Conforming bugzilla@jessica.w3.org
- [Bug 10068] Suggest making noscript obsolete but conforming bugzilla@jessica.w3.org
- [Bug 10068] Suggest making noscript obsolete but conforming bugzilla@jessica.w3.org
- [Bug 10068] Suggest making noscript obsolete but conforming bugzilla@jessica.w3.org
- [Bug 10083] Remove references to Microdata from within the document bugzilla@jessica.w3.org
- [Bug 10083] Remove references to Microdata from within the document bugzilla@jessica.w3.org
- [Bug 10083] Remove references to Microdata from within the document bugzilla@jessica.w3.org
- [Bug 10083] Remove references to Microdata from within the document bugzilla@jessica.w3.org
Wednesday, 7 July 2010
- [Bug 10083] Remove references to Microdata from within the document bugzilla@jessica.w3.org
- [Bug 10068] Suggest making noscript obsolete but conforming bugzilla@jessica.w3.org
- [Bug 10104] ssss adas asdsd bugzilla@jessica.w3.org
- [Bug 10068] Suggest making noscript obsolete but conforming bugzilla@jessica.w3.org
- [Bug 10106] New: Define setter for selected bugzilla@jessica.w3.org
- [Bug 10105] New: What about optgroup[disabled]>option? Not :disabled? bugzilla@jessica.w3.org
- [Bug 10068] Suggest making noscript obsolete but conforming bugzilla@jessica.w3.org
- [Bug 10068] Suggest making noscript obsolete but conforming bugzilla@jessica.w3.org
- [Bug 10104] New: ssss adas asdsd bugzilla@jessica.w3.org
- [Bug 10068] Suggest making noscript obsolete but conforming bugzilla@jessica.w3.org
- [Bug 10068] Suggest making noscript obsolete but conforming bugzilla@jessica.w3.org
- [Bug 10068] Suggest making noscript obsolete but conforming bugzilla@jessica.w3.org
- [Bug 10068] Suggest making noscript obsolete but conforming bugzilla@jessica.w3.org
- [Bug 10068] Suggest making noscript obsolete but conforming bugzilla@jessica.w3.org
- [Bug 10068] Suggest making noscript obsolete but conforming bugzilla@jessica.w3.org
- [Bug 10068] Suggest making noscript obsolete but conforming bugzilla@jessica.w3.org
- [Bug 10068] Suggest making noscript obsolete but conforming bugzilla@jessica.w3.org
- [Bug 10068] Suggest making noscript obsolete but conforming bugzilla@jessica.w3.org
- [Bug 10083] Remove references to Microdata from within the document bugzilla@jessica.w3.org
- [Bug 10068] Suggest making noscript obsolete but conforming bugzilla@jessica.w3.org
- [Bug 10083] Remove references to Microdata from within the document bugzilla@jessica.w3.org
- [Bug 10103] New: s/that its namedItem() method returns an HTMLCollection object/that its namedItem() method returns an *HTMLAllCollection* object/ bugzilla@jessica.w3.org
- [Bug 10083] Remove references to Microdata from within the document bugzilla@jessica.w3.org
- [Bug 10083] Remove references to Microdata from within the document bugzilla@jessica.w3.org
- [Bug 10102] New: Can an option element be disabled by a fieldset@disabled ancestor? bugzilla@jessica.w3.org
- [Bug 10101] New: What does non-normative mean? bugzilla@jessica.w3.org
- [Bug 10068] Suggest making noscript obsolete but conforming bugzilla@jessica.w3.org
- [Bug 10068] Deprecate noscript bugzilla@jessica.w3.org
- [Bug 10083] Remove references to Microdata from within the document bugzilla@jessica.w3.org
- [Bug 10083] Remove references to Microdata from within the document bugzilla@jessica.w3.org
- [Bug 10083] Remove references to Microdata from within the document bugzilla@jessica.w3.org
- [Bug 10083] Remove references to Microdata from within the document bugzilla@jessica.w3.org
- [Bug 10083] Remove references to Microdata from within the document bugzilla@jessica.w3.org
- [Bug 10083] Remove references to Microdata from within the document bugzilla@jessica.w3.org
- [Bug 10083] Remove references to Microdata from within the document bugzilla@jessica.w3.org
Tuesday, 6 July 2010
- [Bug 10068] Deprecate noscript bugzilla@jessica.w3.org
- [Bug 10099] "Updates the current entry in the session histor to have" -- "histor" should be "history". bugzilla@jessica.w3.org
- [Bug 10099] New: "Updates the current entry in the session histor to have" -- "histor" should be "history". bugzilla@jessica.w3.org
- [Bug 10091] As far as I can tell, nothing specifies what the intrinsic width/height/ratio for iframes should be. You'd assume it's the height/width/ratio of the document, but of course that's wrong unless the iframe is seamless. bugzilla@jessica.w3.org
- [Bug 10091] As far as I can tell, nothing specifies what the intrinsic width/height/ratio for iframes should be. You'd assume it's the height/width/ratio of the document, but of course that's wrong unless the iframe is seamless. bugzilla@jessica.w3.org
- [Bug 10098] Stray comma or typo in "in cell" "end tag whos name is 'table'" case bugzilla@jessica.w3.org
- [Bug 10098] New: Stray comma or typo in "in cell" "end tag whos name is 'table'" case bugzilla@jessica.w3.org
- [Bug 9122] Obsolete but Conforming bugzilla@jessica.w3.org
- [Bug 9122] Obsolete but Conforming bugzilla@jessica.w3.org
- [Bug 10087] Replace "Obsolete but conforming" by "Deprecated" bugzilla@jessica.w3.org
- [Bug 10091] As far as I can tell, nothing specifies what the intrinsic width/height/ratio for iframes should be. You'd assume it's the height/width/ratio of the document, but of course that's wrong unless the iframe is seamless. bugzilla@jessica.w3.org
- [Bug 10095] "isindex" is ignored inside a form bugzilla@jessica.w3.org
- [Bug 10068] Deprecate noscript bugzilla@jessica.w3.org
- [Bug 10095] "isindex" is ignored inside a form bugzilla@jessica.w3.org
- [Bug 10095] "isindex" is ignored inside a form bugzilla@jessica.w3.org
- [Bug 10096] Adoption Agency 6.4 and 6.5 should be re-ordered bugzilla@jessica.w3.org
- [Bug 10096] Adoption Agency 6.4 and 6.5 should be re-ordered bugzilla@jessica.w3.org
- [Bug 10095] "isindex" is ignored inside a form bugzilla@jessica.w3.org
- [Bug 10096] New: Adoption Agency 6.4 and 6.5 should be re-ordered bugzilla@jessica.w3.org
- [Bug 10094] hello there. if the given context.font string has: "12px/2", shouldnt the evaluated string have "6px"? Otherwise I don't understand what the "/2" means. bugzilla@jessica.w3.org
- [Bug 10091] As far as I can tell, nothing specifies what the intrinsic width/height/ratio for iframes should be. You'd assume it's the height/width/ratio of the document, but of course that's wrong unless the iframe is seamless. bugzilla@jessica.w3.org
- [Bug 10095] "isindex" is ignored inside a form bugzilla@jessica.w3.org
- [Bug 10095] New: "isindex" is ignored inside a form bugzilla@jessica.w3.org
- [Bug 10094] New: hello there. if the given context.font string has: "12px/2", shouldnt the evaluated string have "6px"? Otherwise I don't understand what the "/2" means. bugzilla@jessica.w3.org
Monday, 5 July 2010
- [Bug 10093] New: Typo: "either the element's end tag is parsed on the parser detects" should be "is parsed _or_ the parser detects" bugzilla@jessica.w3.org
- [Bug 10092] "The transitive closure of all the browsing contexts that are directly reachable browsing contexts forms a unit of related browsing contexts." Since a browsing context is not a directly reachable browsing context of itself, this means that top-level brow bugzilla@jessica.w3.org
- [Bug 10092] New: "The transitive closure of all the browsing contexts that are directly reachable browsing contexts forms a unit of related browsing contexts." Since a browsing context is not a directly reachable browsing context of itself, this means that top-level brow bugzilla@jessica.w3.org
- [Bug 10091] As far as I can tell, nothing specifies what the intrinsic width/height/ratio for iframes should be. You'd assume it's the height/width/ratio of the document, but of course that's wrong unless the iframe is seamless. bugzilla@jessica.w3.org
- [Bug 10091] New: As far as I can tell, nothing specifies what the intrinsic width/height/ratio for iframes should be. You'd assume it's the height/width/ratio of the document, but of course that's wrong unless the iframe is seamless. bugzilla@jessica.w3.org
- [Bug 10090] "Removing then, or removing the entire sandbox attribute" -- should "then" be "them"? bugzilla@jessica.w3.org
- [Bug 10090] New: "Removing then, or removing the entire sandbox attribute" -- should "then" be "them"? bugzilla@jessica.w3.org
- [Bug 10083] Remove references to Microdata from within the document bugzilla@jessica.w3.org
- [Bug 10083] Remove references to Microdata from within the document bugzilla@jessica.w3.org
- [Bug 10087] Replace "Obsolete but conforming" by "Deprecated" bugzilla@jessica.w3.org
- [Bug 9122] Obsolete but Conforming bugzilla@jessica.w3.org
- [Bug 10068] Deprecate noscript bugzilla@jessica.w3.org
- [Bug 10085] should say what happens for negative values. test: http://philip.html5.org/tests/canvas/suite/tests/2d.strokeRect.negative.html bugzilla@jessica.w3.org
- [Bug 10086] What if width and height are negative? I believe this should be specified. bugzilla@jessica.w3.org
- [Bug 10087] New: Replace "Obsolete but conforming" by "Deprecated" bugzilla@jessica.w3.org
- [Bug 10086] New: What if width and height are negative? I believe this should be specified. bugzilla@jessica.w3.org
- [Bug 10068] Deprecate noscript bugzilla@jessica.w3.org
- [Bug 10068] Deprecate noscript bugzilla@jessica.w3.org
- [Bug 10084] Please consider adding a section on Chair recusal in deciding escalated issues bugzilla@jessica.w3.org
- [Bug 10085] New: should say what happens for negative values. test: http://philip.html5.org/tests/canvas/suite/tests/2d.strokeRect.negative.html bugzilla@jessica.w3.org
- [Bug 10080] "in body" insertion mode, "any other end tag", step 2.2 seems wrong. bugzilla@jessica.w3.org
- [Bug 10071] there should be a 'stop()' method or a 'clear()' method to clear the currently playing media because pause() doesnt clear it and setting the src to an empty string or null doesnt work bugzilla@jessica.w3.org
- [Bug 10084] Please consider adding a section on Chair recusal in deciding escalated issues bugzilla@jessica.w3.org
- [Bug 10084] New: Please consider adding a section on Chair recusal in deciding escalated issue bugzilla@jessica.w3.org
- [Bug 10068] Deprecate noscript bugzilla@jessica.w3.org
- [Bug 10083] Remove references to Microdata from within the document bugzilla@jessica.w3.org
- [Bug 10083] Remove references to Microdata from within the document bugzilla@jessica.w3.org
- [Bug 10083] New: Remove references to Microdata from within the document bugzilla@jessica.w3.org
- [Bug 10063] Foster Parenting Paragraph is confusing bugzilla@jessica.w3.org
- [Bug 10080] "in body" insertion mode, "any other end tag", step 2.2 seems wrong. bugzilla@jessica.w3.org
- [Bug 10078] Step 2.2 of "in body" "any other end tag" seems wrong. bugzilla@jessica.w3.org
- [Bug 10082] New: s/then the name argument/then the target argument/ bugzilla@jessica.w3.org
- [Bug 10081] Okay, so could you add a note explaining what kind of active Document is *not* "fully active"? After reading very carefully for a few minutes and pondering a bit, I *think* it would be a Document that is the active Document of its browsing context, but w bugzilla@jessica.w3.org
- [Bug 10081] New: Okay, so could you add a note explaining what kind of active Document is *not* "fully active"? After reading very carefully for a few minutes and pondering a bit, I *think* it would be a Document that is the active Document of its browsing context, but w bugzilla@jessica.w3.org
Sunday, 4 July 2010
- [Bug 10078] Step 2.2 of "in body" "any other end tag" seems wrong. bugzilla@jessica.w3.org
- [Bug 10079] Step 2.2 of "in body" "any other end tag" seems wrong. bugzilla@jessica.w3.org
- [Bug 10063] Foster Parenting Paragraph is confusing bugzilla@jessica.w3.org
- [Bug 10080] New: "in body" insertion mode, "any other end tag", step 2.2 seems wrong. bugzilla@jessica.w3.org
- [Bug 10079] New: Step 2.2 of "in body" "any other end tag" seems wrong. bugzilla@jessica.w3.org
- [Bug 10078] New: Step 2.2 of "in body" "any other end tag" seems wrong. bugzilla@jessica.w3.org
- [Bug 10077] New: The <embed> should support an alt attribute. While the embedded content should provide for accessilibility of the embedded object, the developer doesn't always have control over those content, some embeddable formats are inherently less accessible, and th bugzilla@jessica.w3.org
- [Bug 9958] The DOCTYPE paragraph must explain and define the DOCTYPE rules better and more generally bugzilla@jessica.w3.org
- [Bug 9631] Change name of <figcaption> to <summary> bugzilla@jessica.w3.org
- [Bug 10063] Foster Parenting Paragraph is confusing bugzilla@jessica.w3.org
- [Bug 9631] Change name of <figcaption> to <summary> bugzilla@jessica.w3.org
- [Bug 9631] Change name of <figcaption> to <summary> bugzilla@jessica.w3.org
- [Bug 9631] Change name of <figcaption> to <summary> bugzilla@jessica.w3.org
Saturday, 3 July 2010
- [Bug 10075] New: specify that polyglot docs do not contain xml:space or xml:base attributes bugzilla@jessica.w3.org
- [Bug 8946] H:TML title is confusing bugzilla@jessica.w3.org
- [Bug 8835] Clarifcation of the purpose of "Markup" spec and possible renaming of it. bugzilla@jessica.w3.org
- [Bug 8835] Clarifcation of the purpose of "Markup" spec and possible renaming of it. bugzilla@jessica.w3.org
- [Bug 8835] Clarifcation of the purpose of "Markup" spec and possible renaming of it. bugzilla@jessica.w3.org
- [Bug 8946] H:TML title is confusing bugzilla@jessica.w3.org
- [Bug 8946] H:TML title is confusing bugzilla@jessica.w3.org
- [Bug 10071] New: there should be a 'stop()' method or a 'clear()' method to clear the currently playing media because pause() doesnt clear it and setting the src to an empty string or null doesnt work bugzilla@jessica.w3.org
Friday, 2 July 2010
- [Bug 10068] Deprecate noscript bugzilla@jessica.w3.org
- [Bug 10070] New: s/this specifications says/this specification says/ bugzilla@jessica.w3.org
- [Bug 10069] New: Structured clone algorithm should throw something more informative than NOT_SUPPORTED_ERR bugzilla@jessica.w3.org
- [Bug 10020] s/The WebSRTs format/The WebSRT format/? bugzilla@jessica.w3.org
- [Bug 10050] Q should be quotation or "quote." Otherwise footer whould be "F" and Header should be "H." bugzilla@jessica.w3.org
- [Bug 10020] s/The WebSRTs format/The WebSRT format/? bugzilla@jessica.w3.org
- [Bug 10068] Deprecate noscript bugzilla@jessica.w3.org
- [Bug 10068] New: Deprecate noscript bugzilla@jessica.w3.org
- [Bug 10066] replace section 3.2.6 with the alternative spec text provided bugzilla@jessica.w3.org
- [Bug 10067] this only lists entities whose replacement text is a single character, for example many of the negated operators, for example bugzilla@jessica.w3.org
- [Bug 10067] New: this only lists entities whose replacement text is a single character, for example many of the negated operators, for example bugzilla@jessica.w3.org
- [Bug 10066] New: replace section 3.2.6 with the alternative spec text provided bugzilla@jessica.w3.org
- [Bug 10063] When is it ever possible for the last table element to have a parent who is not an element? bugzilla@jessica.w3.org
- [Bug 10063] When is it ever possible for the last table element to have a parent who is not an element? bugzilla@jessica.w3.org
- [Bug 10063] When is it ever possible for the last table element to have a parent who is not an element? bugzilla@jessica.w3.org
- [Bug 10063] New: When is it ever possible for the last table element to have a parent who is not an element? bugzilla@jessica.w3.org
Thursday, 1 July 2010
- [Bug 10062] "If the attribute is specified, the attribute's value must be the ID of a . . ." No algorithm is given for what it means to "be the ID" of an element. bugzilla@jessica.w3.org
- [Bug 10062] "If the attribute is specified, the attribute's value must be the ID of a . . ." No algorithm is given for what it means to "be the ID" of an element. bugzilla@jessica.w3.org
- [Bug 10062] New: "If the attribute is specified, the attribute's value must be the ID of a . . ." No algorithm is given for what it means to "be the ID" of an element. bugzilla@jessica.w3.org
- [Bug 10061] New: rt and rp elements end tags should not be allowed to be omitted bugzilla@jessica.w3.org
- [Bug 9901] co-chairs should also address objections raised in change proposals bugzilla@jessica.w3.org
- [Bug 9979] Why can't a value start out incomplete, e.g. "2010-" ? bugzilla@jessica.w3.org
- [Bug 10059] New: should allow a line terminator between </rt> and </ruby> bugzilla@jessica.w3.org
- [Bug 10057] New: I do not like the "or do nothing" part, as the label is an really good aid for aiming at small form elemnts like a checkbox or radiobutton. bugzilla@jessica.w3.org

Last message date: Saturday, 31 July 2010 21:48:28 GMT
Archived on: Saturday, 31 July 2010 21:48:34 GMT

public-html-bugzilla@w3.org from July 2010 by date