Thursday, 31 March 2011
Wednesday, 30 March 2011
Tuesday, 29 March 2011
Monday, 28 March 2011
Sunday, 27 March 2011
Saturday, 26 March 2011
Friday, 25 March 2011
Thursday, 24 March 2011
Wednesday, 23 March 2011
Tuesday, 22 March 2011
- [Bug 12365] Add @fullsize to <img> bugzilla@jessica.w3.org
- [Bug 12365] Add @fullsize to <img> bugzilla@jessica.w3.org
- [Bug 12365] Add @fullsize to <img> bugzilla@jessica.w3.org
- [Bug 12365] Add @fullsize to <img> bugzilla@jessica.w3.org
- [Bug 12365] Add @fullsize to <img> bugzilla@jessica.w3.org
- [Bug 12271] <input list=""> needs an event triggered on selection of suggestion bugzilla@jessica.w3.org
- [Bug 12271] <input list=""> needs an event triggered on selection of suggestion bugzilla@jessica.w3.org
- [Bug 12365] Add @fullsize to <img> bugzilla@jessica.w3.org
- [Bug 12365] Add @fullsize to <img> bugzilla@jessica.w3.org
- [Bug 12271] <input list=""> needs an event triggered on selection of suggestion bugzilla@jessica.w3.org
- [Bug 12365] New: Add @fullsize to <img> bugzilla@jessica.w3.org
- [Bug 12243] Warn when ARIA-describedby/-labelledby points to interactive/form associated content bugzilla@jessica.w3.org
- [Bug 12243] Warn when ARIA-describedby/-labelledby points to interactive/form associated content bugzilla@jessica.w3.org
- [Bug 12243] Warn when ARIA-describedby/-labelledby points to interactive/form associated content bugzilla@jessica.w3.org
- [Bug 12362] test test test tets bugzilla@jessica.w3.org
- [Bug 10419] <video> should allow muted as a content attribute bugzilla@jessica.w3.org
- [Bug 12271] <input list=""> needs an event triggered on selection of suggestion bugzilla@jessica.w3.org
- [Bug 12363] Include @longdesc in Microdata bugzilla@jessica.w3.org
- [Bug 12245] @size on <select> drop-downs is not enough to specify the drop-down maxlength on long options lists with scrollbars bugzilla@jessica.w3.org
- [Bug 12364] which is "the first selected video track"? bugzilla@jessica.w3.org
- [Bug 12364] New: which is "the first selected video track"? bugzilla@jessica.w3.org
- [Bug 12363] Include @longdesc in Microdata bugzilla@jessica.w3.org
- [Bug 10911] Datalist descendants shouldn't be barred from constraint validation bugzilla@jessica.w3.org
- [Bug 12363] New: Include @longdesc in Microdata bugzilla@jessica.w3.org
- [Bug 12297] Please specify how to handle space, tab and carriage return in title attribute values bugzilla@jessica.w3.org
- [Bug 12296] Rules for parsing an integer don't match ES parseInt() bugzilla@jessica.w3.org
- [Bug 12362] New: test test test tets bugzilla@jessica.w3.org
- [Bug 12361] The "implementation status" for the events doesn't seem to be up to date. For example the canplaythrough event seems to work in Chrome, even though the status says it's not supported by any browser. bugzilla@jessica.w3.org
- [Bug 12288] select.size should be limited to non-negative numbers instead of non-negative numbers greater than zero bugzilla@jessica.w3.org
- [Bug 12361] The "implementation status" for the events doesn't seem to be up to date. For example the canplaythrough event seems to work in Chrome, even though the status says it's not supported by any browser. bugzilla@jessica.w3.org
- [Bug 12361] The "implementation status" for the events doesn't seem to be up to date. For example the canplaythrough event seems to work in Chrome, even though the status says it's not supported by any browser. bugzilla@jessica.w3.org
- [Bug 12361] New: The "implementation status" for the events doesn't seem to be up to date. For example the canplaythrough event seems to work in Chrome, even though the status says it's not supported by any browser. bugzilla@jessica.w3.org
- [Bug 12285] setInterval should clamp to 4ms like setTimeout does, not 10ms bugzilla@jessica.w3.org
- [Bug 12243] Warn when ARIA-describedby/-labelledby points to interactive/form associated content bugzilla@jessica.w3.org
- [Bug 12245] @size on <select> drop-downs is not enough to specify the drop-down maxlength on long options lists with scrollbars bugzilla@jessica.w3.org
- [Bug 12271] <input list=""> needs an event triggered on selection of suggestion bugzilla@jessica.w3.org
- [Bug 12271] <input list=""> needs an event triggered on selection of suggestion bugzilla@jessica.w3.org
- [Bug 12269] If step is the required increase or decrease of the value, is there any way to declare the value used by stepUp() and stepDown()? I had been using step as the number to increase/decrease the value when the up/down arrows were clicked in Chrome, but new bu bugzilla@jessica.w3.org
- [Bug 12267] Make video state transitions happen in the same task as firing events bugzilla@jessica.w3.org
- [Bug 12262] select(), selectionStart, selectionEnd and setSelectionRange() should apply to <input type='email'> bugzilla@jessica.w3.org
- [Bug 12256] <input type=number value=""> should be valid? bugzilla@jessica.w3.org
- [Bug 12255] option.label and option.value could be consistent bugzilla@jessica.w3.org
- [Bug 12254] Investigate if <progress> element wouldn't need to be form-associated element bugzilla@jessica.w3.org
- [Bug 12251] The idea of limited-scope style elements is useful, but it causes compability issues. Current browsers ignore the scope attribute and apply the style to the entire document. It is probably better (safe) to ignore a style sheet that is meant to be scoped t bugzilla@jessica.w3.org
- [Bug 12245] @size on <select> drop-downs is not enough to specify the drop-down maxlength on long options lists with scrollbars bugzilla@jessica.w3.org
Monday, 21 March 2011
- [Bug 12243] Warn when ARIA-describedby/-labelledby points to interactive/form associated content bugzilla@jessica.w3.org
- [Bug 12241] Should form="" always make the input unassociated? bugzilla@jessica.w3.org
- [Bug 11960] Consider making the global scope pollution by names/ids quirks-only bugzilla@jessica.w3.org
- [Bug 12360] New: It seems more accurate to say that the media element "is not currently playing" instead of saying "is paused or not". The phrase "is paused" seems to imply that it's been manually paused by the user, but this would not apply when a page is first viewed an bugzilla@jessica.w3.org
- [Bug 12359] If the content model says it can only contain dt and dd elements then why does it say further down "if a dl contains [...] elements other than dt and dd [...]? bugzilla@jessica.w3.org
- [Bug 12356] Shouldn't the widely deployed rel="copyright" be used instead of rel="license", or at least defined as a synonym for it. bugzilla@jessica.w3.org
- [Bug 12355] It would be great to be eable to "scope" some styles but with a CSS file, not into the HTML code itself. What about a src attribute on style, a scoped attribute on link tag, or some specific syntax into the CSS file ? bugzilla@jessica.w3.org
- [Bug 12352] Is a list of name/value pairs a valid table, even though it is technically only a one-dimensional associative array, since it requires two columns? bugzilla@jessica.w3.org
- [Bug 12349] Should mention that anywhere that expects flow content implicitly also expects phrasing content, and so forth for embedded content. bugzilla@jessica.w3.org
- [Bug 12347] Add textarea { resize: both; } bugzilla@jessica.w3.org
- [Bug 12359] If the content model says it can only contain dt and dd elements then why does it say further down "if a dl contains [...] elements other than dt and dd [...]? bugzilla@jessica.w3.org
- [Bug 12359] New: If the content model says it can only contain dt and dd elements then why does it say further down "if a dl contains [...] elements other than dt and dd [...]? bugzilla@jessica.w3.org
- [Bug 10152] [polyglot] i18n comment 5 : Mention lang and xml:lang bugzilla@jessica.w3.org
- [Bug 10152] [polyglot] i18n comment 5 : Mention lang and xml:lang bugzilla@jessica.w3.org
- [Bug 10152] [polyglot] i18n comment 5 : Mention lang and xml:lang bugzilla@jessica.w3.org
- [Bug 12352] Is a list of name/value pairs a valid table, even though it is technically only a one-dimensional associative array, since it requires two columns? bugzilla@jessica.w3.org
- [Bug 12358] typo: "still have a paused attribute this is true" bugzilla@jessica.w3.org
- [Bug 12358] New: typo: "still have a paused attribute this is true" bugzilla@jessica.w3.org
- [Bug 12357] Text in a MathML text integration point doesn't behave as in an HTML integration point bugzilla@jessica.w3.org
- [Bug 12357] New: Text in a MathML text integration point doesn't behave as in an HTML integration point bugzilla@jessica.w3.org
- [Bug 12356] Shouldn't the widely deployed rel="copyright" be used instead of rel="license", or at least defined as a synonym for it. bugzilla@jessica.w3.org
- [Bug 12356] New: Shouldn't the widely deployed rel="copyright" be used instead of rel="license", or at least defined as a synonym for it. bugzilla@jessica.w3.org
- [Bug 11393] End tag fails to break out of foreign content bugzilla@jessica.w3.org
- [Bug 9452] Handling of additional tracks of a multitrack audio/video resource bugzilla@jessica.w3.org
- [Bug 9452] Handling of additional tracks of a multitrack audio/video resource bugzilla@jessica.w3.org
- [Bug 12355] It would be great to be eable to "scope" some styles but with a CSS file, not into the HTML code itself. What about a src attribute on style, a scoped attribute on link tag, or some specific syntax into the CSS file ? bugzilla@jessica.w3.org
- [Bug 12355] New: It would be great to be eable to "scope" some styles but with a CSS file, not into the HTML code itself. What about a src attribute on style, a scoped attribute on link tag, or some specific syntax into the CSS file ? bugzilla@jessica.w3.org
- [Bug 12339] We should mention that UAs may use a different clock than the wall clock for defining the rate of time in the media timeline, specifically so that they are allowed to use the soundcard clock to ensure reliable audio playback. bugzilla@jessica.w3.org
- [Bug 12339] We should mention that UAs may use a different clock than the wall clock for defining the rate of time in the media timeline, specifically so that they are allowed to use the soundcard clock to ensure reliable audio playback. bugzilla@jessica.w3.org
- [Bug 11812] The align attribute on the td and th elements should be conforming bugzilla@jessica.w3.org
- [Bug 12325] Conformance requirements for <table role=presentation> (layout tables) bugzilla@jessica.w3.org
- [Bug 12354] New: "If the poster attribute's value is the empty string" should also say "or if it is absent", since the algorithm is invoked when the attribute is removed too. bugzilla@jessica.w3.org
- [Bug 12353] New: Is a list of name/value pairs a valid table, even though it is technically only a one-dimensional associative array, since it requires two columns? bugzilla@jessica.w3.org
- [Bug 12352] New: Is a list of name/value pairs a valid table, even though it is technically only a one-dimensional associative array, since it requires two columns? bugzilla@jessica.w3.org
- [Bug 12091] HTMLdocument named-item getter and object fallback bugzilla@jessica.w3.org
- [Bug 12351] New: Consider changing 'the same object' to 'the same such object' when talking about live objects in various places in the spec, for pedantism... bugzilla@jessica.w3.org
- [Bug 12350] New: Should mention that in the "parents" column, categories refer to elements that _expect_ that category, not elements of those categories... bugzilla@jessica.w3.org
- [Bug 12349] New: Should mention that anywhere that expects flow content implicitly also expects phrasing content, and so forth for embedded content. bugzilla@jessica.w3.org
Sunday, 20 March 2011
Saturday, 19 March 2011
Friday, 18 March 2011
Thursday, 17 March 2011
Wednesday, 16 March 2011
- [Bug 12301] Make empty-named radio buttons not belong to a group bugzilla@jessica.w3.org
- [Bug 12319] Typo: outlinee -> outline bugzilla@jessica.w3.org
- [Bug 12319] New: Typo: outlinee -> outline bugzilla@jessica.w3.org
- [Bug 12311] new feature - client side templates bugzilla@jessica.w3.org
- [Bug 12318] New: feature request: a more semantic tag for non-intl-measures? bugzilla@jessica.w3.org
- [Bug 12311] new feature - client side templates bugzilla@jessica.w3.org
- [Bug 12311] new feature - client side templates bugzilla@jessica.w3.org
- [Bug 12311] new feature - client side templates bugzilla@jessica.w3.org
- [Bug 10805] treating single quotes as double quotes not needed for compatibility with existing content bugzilla@jessica.w3.org
- [Bug 12312] This says "The codecs parameter, which certain MIME types define, might be necessary to specify exactly how the resource is encoded." Is this completely up to the browser to decide? Are there any instructions for browsers on how to respond if the codecs a bugzilla@jessica.w3.org
- [Bug 12317] New: Case for NULL character is missing the text "Create a new DOCTYPE token." bugzilla@jessica.w3.org
- [Bug 12312] This says "The codecs parameter, which certain MIME types define, might be necessary to specify exactly how the resource is encoded." Is this completely up to the browser to decide? Are there any instructions for browsers on how to respond if the codecs a bugzilla@jessica.w3.org
- [Bug 12316] New: We should add a checksum here to make it impossible for attackers to modify messages en-route. The HMAC-SHA1 of the cyphertext using as a key the HMAC-SHA1 of ice-key + a second salt should be sufficient. See also http://krijnhoetmer.nl/irc-logs/whatwg/20 bugzilla@jessica.w3.org
- [Bug 12315] New: The definition of the CLOSED state should be changed to only refer to the case of close() being called. bugzilla@jessica.w3.org
- [Bug 12314] New: A PeerConnection shouldn't go into the CLOSED state when all the media streams are closed. Let's leave that for the higher-level protocol, and just assume that ICE will be torn down abruptly if it is closed. bugzilla@jessica.w3.org
- [Bug 12313] New: if a PeerConnection receives a new stream, then has close() called on it before the addstream event fires, the remoteStreams will change between close() and the close event. We should avoid that, probably by checking the readiness state in the event for t bugzilla@jessica.w3.org
- [Bug 12312] New: This says "The codecs parameter, which certain MIME types define, might be necessary to specify exactly how the resource is encoded." Is this completely up to the browser to decide? Are there any instructions for browsers on how to respond if the codecs a bugzilla@jessica.w3.org
- [Bug 12311] New: new feature - client side templates bugzilla@jessica.w3.org
- [Bug 12306] "When authors use the canvas element, they must also provide content that, when presented to the user, conveys essentially the same function or purpose as the bitmap canvas." While everyone can probably agree that alternative content is a good idea when f bugzilla@jessica.w3.org
Tuesday, 15 March 2011
- [Bug 12151] :in-range and :out-of-range should only apply to input elements with a type for which min or max apply bugzilla@jessica.w3.org
- [Bug 12309] Need to taint canvas when a non-CORS cross-site font is in the .font bugzilla@jessica.w3.org
- [Bug 10913] Input element's value should not be sanitized during parsing bugzilla@jessica.w3.org
- [Bug 10912] <output> should not be barred from constraint validation bugzilla@jessica.w3.org
- [Bug 10910] Submit controls should be barred from constraint validation in favor of a new pseudo-class bugzilla@jessica.w3.org
- [Bug 10908] :enabled and :disabled should apply on <fieldset> and <optgroup> bugzilla@jessica.w3.org
- [Bug 10911] Datalist descendants shouldn't be barred from constraint validation bugzilla@jessica.w3.org
- [Bug 12154] b and strong are font-weight: bolder in implementations, not font-weight: bold bugzilla@jessica.w3.org
- [Bug 12306] "When authors use the canvas element, they must also provide content that, when presented to the user, conveys essentially the same function or purpose as the bitmap canvas." While everyone can probably agree that alternative content is a good idea when f bugzilla@jessica.w3.org
- [Bug 12309] New: Need to taint canvas when a non-CORS cross-site font is in the .font bugzilla@jessica.w3.org
- [Bug 12308] Test my comment hello. bugzilla@jessica.w3.org
- [Bug 12154] b and strong are font-weight: bolder in implementations, not font-weight: bold bugzilla@jessica.w3.org
- [Bug 12308] New: Test my comment hello. bugzilla@jessica.w3.org
- [Bug 12305] how about presenting date and time in local format to the user? bugzilla@jessica.w3.org
- [Bug 10804] charset sniffing: please describe the incompatibility bugzilla@jessica.w3.org
- [Bug 10805] treating single quotes as double quotes not needed for compatibility with existing content bugzilla@jessica.w3.org
- [Bug 12306] New: "When authors use the canvas element, they must also provide content that, when presented to the user, conveys essentially the same function or purpose as the bitmap canvas." While everyone can probably agree that alternative content is a good idea when f bugzilla@jessica.w3.org
- [Bug 12305] New: how about presenting date and time in local format to the user? bugzilla@jessica.w3.org
- [Bug 12304] New: Would be nicer if PAUSED was defined on Stream instead of GeneratedStream bugzilla@jessica.w3.org
- [Bug 12303] New: TextTrack is missing an IDL attribute for @default bugzilla@jessica.w3.org
- [Bug 10015] longdesc URL checking bugzilla@jessica.w3.org
- [Bug 10019] Native user agent support for exposing longdesc to all users bugzilla@jessica.w3.org
- [Bug 12302] New: normatively refers to but does not include MouseEvent bugzilla@jessica.w3.org
- [Bug 11958] [device] Use "peripheral" as the base generic device class keyword bugzilla@jessica.w3.org
- [Bug 11935] [device] There is no mention of <device> in the parsing algorithm. Could you please add it to the list of self-closing tags. bugzilla@jessica.w3.org
- [Bug 11802] [device] Suggestion for how to filter the list bugzilla@jessica.w3.org
- [Bug 11673] Streaming audio data from a microphone over a WebSocket bugzilla@jessica.w3.org
- [Bug 12158] [device] It might be useful to have access to USB joysticks (maybe even with force-feedback) and other kinds of HID. bugzilla@jessica.w3.org
- [Bug 11801] [device] I think that for usb, some more desired use cases like smart card login and joystick support, would help adapt the proposal. bugzilla@jessica.w3.org
- [Bug 11707] [device] Developers only need video and audio streams. The type attribute should either be video or audio. bugzilla@jessica.w3.org
- [Bug 12301] New: Make empty-named radio buttons not belong to a group bugzilla@jessica.w3.org
- [Bug 10019] Native user agent support for exposing longdesc to all users bugzilla@jessica.w3.org
- [Bug 10015] longdesc URL checking bugzilla@jessica.w3.org
Monday, 14 March 2011
- [Bug 12297] Please specify how to handle space, tab and carriage return in title attribute values bugzilla@jessica.w3.org
- [Bug 12278] [polyglot] i18n: Make lang and xml:lang required on the root element. bugzilla@jessica.w3.org
- [Bug 12279] [polyglot] Add section on http-equiv and HTTP bugzilla@jessica.w3.org
- [Bug 12299] The (normative and non-normative) assertion that tokenlist.item(index) / tokenlist[index] returns null for index>=length appears to be in conflict with WebIDL, at least for the index property case; afaict WebIDL requires that index property getters throw bugzilla@jessica.w3.org
- [Bug 12279] [polyglot] Add section on http-equiv and HTTP bugzilla@jessica.w3.org
- [Bug 12279] [polyglot] Add section on http-equiv and HTTP bugzilla@jessica.w3.org
- [Bug 12278] [polyglot] i18n: Make lang and xml:lang required on the root element. bugzilla@jessica.w3.org
- [Bug 12279] [polyglot] Add section on http-equiv and HTTP bugzilla@jessica.w3.org
- [Bug 12279] [polyglot] Add section on http-equiv and HTTP bugzilla@jessica.w3.org
- [Bug 12279] [polyglot] Add section on http-equiv and HTTP bugzilla@jessica.w3.org
- [Bug 12279] [polyglot] Add section on http-equiv and HTTP bugzilla@jessica.w3.org
- [Bug 12279] [polyglot] Add section on http-equiv and HTTP bugzilla@jessica.w3.org
- [Bug 12299] The (normative and non-normative) assertion that tokenlist.item(index) / tokenlist[index] returns null for index>=length appears to be in conflict with WebIDL, at least for the index property case; afaict WebIDL requires that index property getters throw bugzilla@jessica.w3.org
- [Bug 12299] The (normative and non-normative) assertion that tokenlist.item(index) / tokenlist[index] returns null for index>=length appears to be in conflict with WebIDL, at least for the index property case; afaict WebIDL requires that index property getters throw bugzilla@jessica.w3.org
- [Bug 11871] type.delete.html to become invalid bugzilla@jessica.w3.org
- [Bug 12296] Rules for parsing an integer don't match ES parseInt() bugzilla@jessica.w3.org
- [Bug 12220] Make sure rules for parsing a float are the same in HTML and in Javascript specifications bugzilla@jessica.w3.org
- [Bug 12296] Rules for parsing an integer don't match ES parseInt() bugzilla@jessica.w3.org
- [Bug 12296] Rules for parsing an integer don't match ES parseInt() bugzilla@jessica.w3.org
- [Bug 12293] Syntax error in the example, the INPUT start tag ends in /> bugzilla@jessica.w3.org
- [Bug 12220] Make sure rules for parsing a float are the same in HTML and in Javascript specifications bugzilla@jessica.w3.org
- [Bug 12296] Rules for parsing an integer don't match ES parseInt() bugzilla@jessica.w3.org
- [Bug 12296] Whitespace handling here doesn't match ES, or Gecko, or Opera. Is there some reason to not just say it works the same as parseInt? Test case alerts 2 in Firefox and Opera (like parseInt()), 0 in Chrome: data:text/html,<!doctype html><input tabindex="&nb bugzilla@jessica.w3.org
- [Bug 12220] Make sure rules for parsing a float are the same in HTML and in Javascript specifications bugzilla@jessica.w3.org
- [Bug 12296] Whitespace handling here doesn't match ES, or Gecko, or Opera. Is there some reason to not just say it works the same as parseInt? Test case alerts 2 in Firefox and Opera (like parseInt()), 0 in Chrome: data:text/html,<!doctype html><input tabindex="&nb bugzilla@jessica.w3.org
- [Bug 12299] The (normative and non-normative) assertion that tokenlist.item(index) / tokenlist[index] returns null for index>=length appears to be in conflict with WebIDL, at least for the index property case; afaict WebIDL requires that index property getters throw bugzilla@jessica.w3.org
- [Bug 10019] Native user agent support for exposing longdesc to all users bugzilla@jessica.w3.org
- [Bug 12299] The (normative and non-normative) assertion that tokenlist.item(index) / tokenlist[index] returns null for index>=length appears to be in conflict with WebIDL, at least for the index property case; afaict WebIDL requires that index property getters throw bugzilla@jessica.w3.org
- [Bug 10019] Native user agent support for exposing longdesc to all users bugzilla@jessica.w3.org
- [Bug 10019] Native user agent support for exposing longdesc to all users bugzilla@jessica.w3.org
- [Bug 10015] longdesc URL checking bugzilla@jessica.w3.org
- [Bug 10015] longdesc URL checking bugzilla@jessica.w3.org
- [Bug 12299] The (normative and non-normative) assertion that tokenlist.item(index) / tokenlist[index] returns null for index>=length appears to be in conflict with WebIDL, at least for the index property case; afaict WebIDL requires that index property getters throw bugzilla@jessica.w3.org
- [Bug 12299] The (normative and non-normative) assertion that tokenlist.item(index) / tokenlist[index] returns null for index>=length appears to be in conflict with WebIDL, at least for the index property case; afaict WebIDL requires that index property getters throw bugzilla@jessica.w3.org
- [Bug 12277] Need to check whether browsers follow this (or are willing to), and if so, spec it: http://hacks.mozilla.org/2011/03/history-api-changes-in-firefox-4/ bugzilla@jessica.w3.org
- [Bug 12299] The (normative and non-normative) assertion that tokenlist.item(index) / tokenlist[index] returns null for index>=length appears to be in conflict with WebIDL, at least for the index property case; afaict WebIDL requires that index property getters throw bugzilla@jessica.w3.org
- [Bug 12299] New: The (normative and non-normative) assertion that tokenlist.item(index) / tokenlist[index] returns null for index>=length appears to be in conflict with WebIDL, at least for the index property case; afaict WebIDL requires that index property getters throw bugzilla@jessica.w3.org
- [Bug 12297] Please specify how to handle space, tab and carriage return in title attribute values bugzilla@jessica.w3.org
- [Bug 12297] Please specify how to handle space, tab and carriage return in title attribute values bugzilla@jessica.w3.org
- [Bug 12298] New: wrong interface referenced in index - interfaces - "col" element bugzilla@jessica.w3.org
- [Bug 12297] Please specify how to handle space, tab and carriage return in title attribute values bugzilla@jessica.w3.org
- [Bug 12297] New: Please specify how to handle space, tab and carriage return in title attribute values bugzilla@jessica.w3.org
- [Bug 11960] Consider making the global scope pollution by names/ids quirks-only bugzilla@jessica.w3.org
- [Bug 11871] type.delete.html to become invalid bugzilla@jessica.w3.org
- [Bug 12288] select.size should be limited to non-negative numbers instead of non-negative numbers greater than zero bugzilla@jessica.w3.org
Sunday, 13 March 2011
- [Bug 11637] Disallow abusing the Decision Policy by escalating editorial bugs bugzilla@jessica.w3.org
- [Bug 12296] Whitespace handling here doesn't match ES, or Gecko, or Opera. Is there some reason to not just say it works the same as parseInt? Test case alerts 2 in Firefox and Opera (like parseInt()), 0 in Chrome: data:text/html,<!doctype html><input tabindex="&nb bugzilla@jessica.w3.org
- [Bug 12296] New: Whitespace handling here doesn't match ES, or Gecko, or Opera. Is there some reason to not just say it works the same as parseInt? Test case alerts 2 in Firefox and Opera (like parseInt()), 0 in Chrome: data:text/html,<!doctype html><input tabindex="&nb bugzilla@jessica.w3.org
- [Bug 12293] Syntax error in the example, the INPUT start tag ends in /> bugzilla@jessica.w3.org
- [Bug 12293] Syntax error in the example, the INPUT start tag ends in /> bugzilla@jessica.w3.org
- [Bug 12292] Use of <teaser> or similar construct for a reference to an external article. bugzilla@jessica.w3.org
- [Bug 12293] New: Syntax error in the example, the INPUT start tag ends in /> bugzilla@jessica.w3.org
- [Bug 12235] Make <xmp> conforming bugzilla@jessica.w3.org
- [Bug 12062] UTF-8 BOM should not be forbidden in Polyglot Markup bugzilla@jessica.w3.org
- [Bug 12292] New: Use of <teaser> or similar construct for a reference to an external article. bugzilla@jessica.w3.org
Saturday, 12 March 2011
Friday, 11 March 2011
Thursday, 10 March 2011
- [Bug 12285] setInterval should clamp to 4ms like setTimeout does, not 10ms bugzilla@jessica.w3.org
- [Bug 12285] New: setInterval should clamp to 4ms like setTimeout does, not 10ms bugzilla@jessica.w3.org
- [Bug 12267] Make video state transitions happen in the same task as firing events bugzilla@jessica.w3.org
- [Bug 12267] Make video state transitions happen in the same task as firing events bugzilla@jessica.w3.org
- [Bug 12267] Make video state transitions happen in the same task as firing events bugzilla@jessica.w3.org
- [Bug 12267] Make video state transitions happen in the same task as firing events bugzilla@jessica.w3.org
- [Bug 10963] Table prohibited from being used as a layout aid bugzilla@jessica.w3.org
- [Bug 8449] Remove extraneous material from Table section bugzilla@jessica.w3.org
- [Bug 12283] No indication of parsing error 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 12284] How about call the new standard "HML". Then my "C" program won't have to check for a '4 or 3' character word. we will already know the word is 3 characters. bugzilla@jessica.w3.org
- [Bug 8659] Media events to indicate captions and audio descriptions bugzilla@jessica.w3.org
- [Bug 12267] Make video state transitions happen in the same task as firing events bugzilla@jessica.w3.org
- [Bug 12267] Make video state transitions happen in the same task as firing events bugzilla@jessica.w3.org
- [Bug 12284] New: How about call the new standard "HML". Then my "C" program won't have to check for a '4 or 3' character word. we will already know the word is 3 characters. bugzilla@jessica.w3.org
- [Bug 12283] New: No indication of parsing error bugzilla@jessica.w3.org
- [Bug 12282] New: If the given browsing context name is _parent, then the chosen browsing context must be the parent browsing context of the current one, unless there isn't one, in which case the chosen browsing context must be the current browsing context. bugzilla@jessica.w3.org
- [Bug 12277] Need to check whether browsers follow this (or are willing to), and if so, spec it: http://hacks.mozilla.org/2011/03/history-api-changes-in-firefox-4/ bugzilla@jessica.w3.org
- [Bug 11637] Disallow abusing the Decision Policy by escalating editorial bugs bugzilla@jessica.w3.org
- [Bug 10230] Decisions need to be made in timely manner bugzilla@jessica.w3.org
- [Bug 11839] window.opener needs to be writable, not readonly (as it is in Gecko, Chrome, IE) bugzilla@jessica.w3.org
- [Bug 12278] [polyglot] i18n: Make lang and xml:lang required on the root element. bugzilla@jessica.w3.org
- [Bug 12279] New: [polyglot] Add section on http-equiv and HTTP bugzilla@jessica.w3.org
- [Bug 8657] Allow UA to reload fallback content if it fails to load bugzilla@jessica.w3.org
- [Bug 8657] Allow UA to reload fallback content if it fails to load bugzilla@jessica.w3.org
- [Bug 10152] [polyglot] i18n comment 5 : Mention lang and xml:lang bugzilla@jessica.w3.org
- [Bug 12278] New: [polyglot] i18n: Make lang and xml:lang required on the root element. bugzilla@jessica.w3.org
Wednesday, 9 March 2011
- [Bug 11839] window.opener needs to be writable, not readonly (as it is in Gecko, Chrome, IE) bugzilla@jessica.w3.org
- [Bug 12277] Need to check whether browsers follow this (or are willing to), and if so, spec it: http://hacks.mozilla.org/2011/03/history-api-changes-in-firefox-4/ bugzilla@jessica.w3.org
- [Bug 12277] New: Need to check whether browsers follow this (or are willing to), and if so, spec it: http://hacks.mozilla.org/2011/03/history-api-changes-in-firefox-4/ bugzilla@jessica.w3.org
- [Bug 12276] New: In the HTTP spec, the and that's what's related to http-equiv, it's Content-Type, not content-type etc.. I think the current definition of http-equiv needs to be revised. bugzilla@jessica.w3.org
- [Bug 12275] New: Null case: Missing "Create a new DOCTYPE token." bugzilla@jessica.w3.org
- [Bug 11637] Disallow abusing the Decision Policy by escalating editorial bugs bugzilla@jessica.w3.org
- [Bug 10152] [polyglot] i18n comment 5 : Mention lang and xml:lang bugzilla@jessica.w3.org
- [Bug 12274] New: Spelling mistakes in a few sections bugzilla@jessica.w3.org
- [Bug 11637] Disallow abusing the Decision Policy by escalating editorial bugs bugzilla@jessica.w3.org
- [Bug 10152] [polyglot] i18n comment 5 : Mention lang and xml:lang bugzilla@jessica.w3.org
- [Bug 10152] [polyglot] i18n comment 5 : Mention lang and xml:lang bugzilla@jessica.w3.org
- [Bug 12273] sda ads asd qwr 12 efg saf 12 fasf bugzilla@jessica.w3.org
- [Bug 12273] New: sda ads asd qwr 12 efg saf 12 fasf bugzilla@jessica.w3.org
- [Bug 10152] [polyglot] i18n comment 5 : Mention lang and xml:lang bugzilla@jessica.w3.org
- [Bug 10152] [polyglot] i18n comment 5 : Mention lang and xml:lang bugzilla@jessica.w3.org
- [Bug 10152] [polyglot] i18n comment 5 : Mention lang and xml:lang bugzilla@jessica.w3.org
- [Bug 10152] [polyglot] i18n comment 5 : Mention lang and xml:lang bugzilla@jessica.w3.org
- [Bug 10152] [polyglot] i18n comment 5 : Mention lang and xml:lang bugzilla@jessica.w3.org
- [Bug 10152] [polyglot] i18n comment 5 : Mention lang and xml:lang bugzilla@jessica.w3.org
- [Bug 10152] [polyglot] i18n comment 5 : Mention lang and xml:lang bugzilla@jessica.w3.org
- [Bug 12271] New: <input list=""> needs an event triggered on selection of suggestion bugzilla@jessica.w3.org
- [Bug 12230] From this algorithm it does not seem to follow that dispatching a synthetic non-canceled submit event at a form causes it to be submitted. Yet that is what browsers implement. So that forms have a default handler for submit events should probably be split bugzilla@jessica.w3.org
- [Bug 12270] New: OnProgress event bugzilla@jessica.w3.org
- [Bug 11637] Disallow abusing the Decision Policy by escalating editorial bugs bugzilla@jessica.w3.org
- [Bug 12267] Make video state transitions happen in the same task as firing events bugzilla@jessica.w3.org
- [Bug 11637] Disallow abusing the Decision Policy by escalating editorial bugs bugzilla@jessica.w3.org
- [Bug 12267] Make video state transitions happen in the same task as firing events bugzilla@jessica.w3.org
- [Bug 11637] Disallow abusing the Decision Policy by escalating editorial bugs bugzilla@jessica.w3.org
- [Bug 12267] Make video state transitions happen in the same task as firing events bugzilla@jessica.w3.org
Tuesday, 8 March 2011
- [Bug 12240] "The values 'true' and 'false' are not allowed on boolean attributes." - this also implies that "false" is not a valid attribute name, since ... false="false" ... (meaning the "false" property is 'true') would not be permitted in XML serialization bugzilla@jessica.w3.org
- [Bug 12269] New: If step is the required increase or decrease of the value, is there any way to declare the value used by stepUp() and stepDown()? I had been using step as the number to increase/decrease the value when the up/down arrows were clicked in Chrome, but new bu bugzilla@jessica.w3.org
- [Bug 12267] Make video state transitions happen in the same task as firing events bugzilla@jessica.w3.org
- [Bug 12267] Make video state transitions happen in the same task as firing events bugzilla@jessica.w3.org
- [Bug 12267] Make video state transitions happen in the same task as firing events bugzilla@jessica.w3.org
- [Bug 12224] Drop rel=pingback. The Pingback spec seems dead and unused, and redundant with the Referer header. bugzilla@jessica.w3.org
- [Bug 11977] HTML5 spec. seems to unnecessarily ban strict mode event handlers bugzilla@jessica.w3.org
- [Bug 12267] Make video state transitions happen in the same task as firing events bugzilla@jessica.w3.org
- [Bug 12240] "The values 'true' and 'false' are not allowed on boolean attributes." - this also implies that "false" is not a valid attribute name, since ... false="false" ... (meaning the "false" property is 'true') would not be permitted in XML serialization bugzilla@jessica.w3.org
- [Bug 12230] From this algorithm it does not seem to follow that dispatching a synthetic non-canceled submit event at a form causes it to be submitted. Yet that is what browsers implement. So that forms have a default handler for submit events should probably be split bugzilla@jessica.w3.org
- [Bug 12230] From this algorithm it does not seem to follow that dispatching a synthetic non-canceled submit event at a form causes it to be submitted. Yet that is what browsers implement. So that forms have a default handler for submit events should probably be split bugzilla@jessica.w3.org
- [Bug 11981] There's a race condition with autoplay if the autoplay attribute is removed in e.g. 'loadstart' event listener bugzilla@jessica.w3.org
- [Bug 11981] There's a race condition with autoplay if the autoplay attribute is removed in e.g. 'loadstart' event listener bugzilla@jessica.w3.org
- [Bug 12195] canplay event is fired long before one can play in any meaningful way bugzilla@jessica.w3.org
- [Bug 12267] Make video state transitions happen in the same task as firing events bugzilla@jessica.w3.org
- [Bug 12267] Make video state transitions happen in the same task as firing events bugzilla@jessica.w3.org
- [Bug 12267] Make video state transitions happen in the same task as firing events bugzilla@jessica.w3.org
- [Bug 12244] Warn when interactive/forms associated content appears inside role=childrenArePresentational elements bugzilla@jessica.w3.org
- [Bug 12243] Warn when ARIA-describedby/-labelledby points to interactive/form associated content 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 12226] incorrect example in section 1.9.2 syntax errors bugzilla@jessica.w3.org
- [Bug 12214] Canvas fallback content implementation is underspecified bugzilla@jessica.w3.org
- [Bug 8736] Decision to playback for media should be left to the user agent bugzilla@jessica.w3.org
- [Bug 5758] <audio> and <video> do not have sufficient support for synchronized accessibility content bugzilla@jessica.w3.org
- [Bug 12267] New: Make video state transitions happen in the same task as firing events bugzilla@jessica.w3.org
- [Bug 12266] íì´ ì¢ì ìë¹ì¤ë¤. bugzilla@jessica.w3.org
- [Bug 12265] Step 3. should s/object's underlying string/DOMTokenList object's underlying string/ for clarity bugzilla@jessica.w3.org
- [Bug 12230] From this algorithm it does not seem to follow that dispatching a synthetic non-canceled submit event at a form causes it to be submitted. Yet that is what browsers implement. So that forms have a default handler for submit events should probably be split bugzilla@jessica.w3.org
- [Bug 12266] New: íì´ ì¢ì ìë¹ì¤ë¤. bugzilla@jessica.w3.org
- [Bug 8658] Availability of captions or additional audio tracks bugzilla@jessica.w3.org
- [Bug 8187] Section 4.8.7 on video makes no reference to audio description bugzilla@jessica.w3.org
- [Bug 12264] Point 3. should state: "Otherwise, split DOMTokenList object's underlying string on spaces to get the list of tokens in the object's underlying string." bugzilla@jessica.w3.org
- [Bug 12264] Point 3. should state: "Otherwise, split DOMTokenList object's underlying string on spaces to get the list of tokens in the object's underlying string." bugzilla@jessica.w3.org
- [Bug 12265] New: Step 3. should s/object's underlying string/DOMTokenList object's underlying string/ for clarity bugzilla@jessica.w3.org
- [Bug 12264] Point 3. ("Otherwise, split the underlying string on spaces to get the list of tokens in the object's underlying string.") is not needed, because after point 2. there are no space characters left. bugzilla@jessica.w3.org
- [Bug 12264] New: Point 3. ("Otherwise, split the underlying string on spaces to get the list of tokens in the object's underlying string.") is not needed, because after point 2. there are no space characters left. bugzilla@jessica.w3.org
- [Bug 12263] New: Worker limitation bugzilla@jessica.w3.org
- [Bug 12230] From this algorithm it does not seem to follow that dispatching a synthetic non-canceled submit event at a form causes it to be submitted. Yet that is what browsers implement. So that forms have a default handler for submit events should probably be split bugzilla@jessica.w3.org
- [Bug 12235] Make <xmp> conforming bugzilla@jessica.w3.org
- [Bug 12101] "Structured clone" can be passed an object with a hostile getter that returns an object identical to itself; "structured clone" does not prevent such an infinite regression. bugzilla@jessica.w3.org
- [Bug 12262] select(), selectionStart, selectionEnd and setSelectionRange() should apply to <input type='email'> bugzilla@jessica.w3.org
- [Bug 12254] Investigate if <progress> element wouldn't need to be form-associated element bugzilla@jessica.w3.org
- [Bug 12262] select(), selectionStart, selectionEnd and setSelectionRange() should apply to <input type='email'> bugzilla@jessica.w3.org
- [Bug 12262] select(), selectionStart, selectionEnd and setSelectionRange() should apply to <input type='email'> bugzilla@jessica.w3.org
- [Bug 12235] Make <xmp> conforming bugzilla@jessica.w3.org
- [Bug 12260] a a a a a a a bugzilla@jessica.w3.org
- [Bug 11637] Disallow abusing the Decision Policy by escalating editorial bugs bugzilla@jessica.w3.org
- [Bug 12262] select(), selectionStart, selectionEnd and setSelectionRange() should apply to <input type='email'> bugzilla@jessica.w3.org
- [Bug 12262] New: select(), selectionStart, selectionEnd and setSelectionRange() should apply to <input type='email'> bugzilla@jessica.w3.org
Monday, 7 March 2011
Sunday, 6 March 2011
Saturday, 5 March 2011
Friday, 4 March 2011
- [Bug 11212] Make all the radio button group suffering from being missing (instead of only radio's with the required attribute) bugzilla@jessica.w3.org
- [Bug 12024] Should make it clear that when an <object> navigates to a resource given in its data="" attribute, the fetching is done by the <object>'s algorithm and _not_ the "navigate" algorithm. In particular, there's a note in the <object> section about appcaches m bugzilla@jessica.w3.org
- [Bug 12024] Should make it clear that when an <object> navigates to a resource given in its data="" attribute, the fetching is done by the <object>'s algorithm and _not_ the "navigate" algorithm. In particular, there's a note in the <object> section about appcaches m bugzilla@jessica.w3.org
- [Bug 12062] UTF-8 BOM should not be forbidden in Polyglot Markup bugzilla@jessica.w3.org
- [Bug 12062] UTF-8 BOM should not be forbidden in Polyglot Markup bugzilla@jessica.w3.org
- [Bug 11956] restrict use of role=presentation bugzilla@jessica.w3.org
- [Bug 11956] restrict use of role=presentation bugzilla@jessica.w3.org
- [Bug 12232] Progress element should be shown vertically when height>width bugzilla@jessica.w3.org
- [Bug 12230] From this algorithm it does not seem to follow that dispatching a synthetic non-canceled submit event at a form causes it to be submitted. Yet that is what browsers implement. So that forms have a default handler for submit events should probably be split bugzilla@jessica.w3.org
- [Bug 11984] Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org
- [Bug 12062] UTF-8 BOM should not be forbidden in Polyglot Markup bugzilla@jessica.w3.org
- [Bug 12241] Should form="" always make the input unassociated? bugzilla@jessica.w3.org
- [Bug 12241] New: Should form="" always make the input unassociated? bugzilla@jessica.w3.org
- [Bug 11956] restrict use of role=presentation bugzilla@jessica.w3.org
- [Bug 11956] restrict use of role=presentation bugzilla@jessica.w3.org
- [Bug 11960] Consider making the global scope pollution by names/ids quirks-only bugzilla@jessica.w3.org
- [Bug 12091] HTMLdocument named-item getter and object fallback bugzilla@jessica.w3.org
- [Bug 12235] Make <xmp> conforming bugzilla@jessica.w3.org
- [Bug 11960] Consider making the global scope pollution by names/ids quirks-only bugzilla@jessica.w3.org
- [Bug 11960] Consider making the global scope pollution by names/ids quirks-only bugzilla@jessica.w3.org
- [Bug 11956] restrict use of role=presentation bugzilla@jessica.w3.org
- [Bug 12235] Make <xmp> conforming bugzilla@jessica.w3.org
- [Bug 11956] restrict use of role=presentation bugzilla@jessica.w3.org
- [Bug 12240] "The values 'true' and 'false' are not allowed on boolean attributes." - this also implies that "false" is not a valid attribute name, since ... false="false" ... (meaning the "false" property is 'true') would not be permitted in XML serialization bugzilla@jessica.w3.org
- [Bug 11960] Consider making the global scope pollution by names/ids quirks-only bugzilla@jessica.w3.org
- [Bug 12165] The requirement on the plaintext element conflicts with its old definition and usage. It is better to avoid requiring any support than to require support that breaks legacy usage. The plaintext element should be regarded as undefined in HTML5. bugzilla@jessica.w3.org
- [Bug 12235] Make <xmp> conforming bugzilla@jessica.w3.org
- [Bug 9452] Handling of additional tracks of a multitrack audio/video resource bugzilla@jessica.w3.org
- [Bug 12239] DrawImage() typographic error bugzilla@jessica.w3.org
- [Bug 12240] "The values 'true' and 'false' are not allowed on boolean attributes." - this also implies that "false" is not a valid attribute name, since ... false="false" ... (meaning the "false" property is 'true') would not be permitted in XML serialization bugzilla@jessica.w3.org
- [Bug 12240] "The values 'true' and 'false' are not allowed on boolean attributes." - this also implies that "false" is not a valid attribute name, since ... false="false" ... (meaning the "false" property is 'true') would not be permitted in XML serialization bugzilla@jessica.w3.org
- [Bug 12240] New: "The values 'true' and 'false' are not allowed on boolean attributes." - this also implies that "false" is not a valid attribute name, since ... false="false" ... (meaning the "false" property is 'true') would not be permitted in XML serialization bugzilla@jessica.w3.org
- [Bug 10723] Support stopping at the time given by a media resource's fragment identifier bugzilla@jessica.w3.org
- [Bug 12239] New: DrawImage() typographic error bugzilla@jessica.w3.org
- [Bug 11452] 4.10.22.5.5. should describe how to send the filename when the field is a file field. It should send the filename as "filename" parameter and its character encoding must be _charset_. bugzilla@jessica.w3.org
- [Bug 10788] @srcdoc in polyglot documents bugzilla@jessica.w3.org
- [Bug 12165] The requirement on the plaintext element conflicts with its old definition and usage. It is better to avoid requiring any support than to require support that breaks legacy usage. The plaintext element should be regarded as undefined in HTML5. bugzilla@jessica.w3.org
- [Bug 11129] Remove forminput, formchange and related dispatch methods bugzilla@jessica.w3.org
- [Bug 12230] From this algorithm it does not seem to follow that dispatching a synthetic non-canceled submit event at a form causes it to be submitted. Yet that is what browsers implement. So that forms have a default handler for submit events should probably be split bugzilla@jessica.w3.org
- [Bug 11956] restrict use of role=presentation bugzilla@jessica.w3.org
- [Bug 12237] New: The MIME type for multipart/form-data needs "boundary=" inserted as well. Please do not make it part of the boundary string by the way. bugzilla@jessica.w3.org
- [Bug 11988] "then set to true." +it bugzilla@jessica.w3.org
- [Bug 12236] New: s/port of a sequence/part of a sequence/ bugzilla@jessica.w3.org
- [Bug 12235] Make <xmp> conforming bugzilla@jessica.w3.org
- [Bug 9452] Handling of additional tracks of a multitrack audio/video resource bugzilla@jessica.w3.org
- [Bug 11977] HTML5 spec. seems to unnecessarily ban strict mode event handlers bugzilla@jessica.w3.org
- [Bug 10723] Support stopping at the time given by a media resource's fragment identifier bugzilla@jessica.w3.org
- [Bug 11960] Consider making the global scope pollution by names/ids quirks-only bugzilla@jessica.w3.org
- [Bug 11298] Surrogate catching doesn't belong in input stream preprocessing bugzilla@jessica.w3.org
- [Bug 12023] How shall invalid code points from U+D800 to U+DFFF be handled - a replacement character U+FFFD REPLACEMENT CHARACTER for each byte or the whole sequence (I assume the latter) bugzilla@jessica.w3.org
- [Bug 11298] Surrogate catching doesn't belong in input stream preprocessing bugzilla@jessica.w3.org
- [Bug 12166] The requirement on the xmp element conflicts with its old definition (which requires a special parsing mode where no markup except the element's end tag is recognized) and usage. It is better to avoid requiring any support than to require support that bre bugzilla@jessica.w3.org
- [Bug 12235] Make <xmp> conforming bugzilla@jessica.w3.org
- [Bug 12235] New: Make <xmp> conforming bugzilla@jessica.w3.org
- [Bug 12167] The requirement on the listing element conflicts with its old definition (which requires a special parsing mode where no markup except the element's end tag is recognized) and usage. It is better to avoid requiring any support than to require support that bugzilla@jessica.w3.org
- [Bug 12165] The requirement on the plaintext element conflicts with its old definition and usage. It is better to avoid requiring any support than to require support that breaks legacy usage. The plaintext element should be regarded as undefined in HTML5. bugzilla@jessica.w3.org
- [Bug 11912] HTML5 provides an opportunity to fix a long-running problem with HTTP Authentication. HTTP Authentication is important, because it is the only way to execute a request with 100% certainty that the user has provided an authentication secret. Furthermore, bugzilla@jessica.w3.org
- [Bug 12166] The requirement on the xmp element conflicts with its old definition (which requires a special parsing mode where no markup except the element's end tag is recognized) and usage. It is better to avoid requiring any support than to require support that bre bugzilla@jessica.w3.org
- [Bug 11912] HTML5 provides an opportunity to fix a long-running problem with HTTP Authentication. HTTP Authentication is important, because it is the only way to execute a request with 100% certainty that the user has provided an authentication secret. Furthermore, bugzilla@jessica.w3.org
- [Bug 11912] HTML5 provides an opportunity to fix a long-running problem with HTTP Authentication. HTTP Authentication is important, because it is the only way to execute a request with 100% certainty that the user has provided an authentication secret. Furthermore, bugzilla@jessica.w3.org
- [Bug 11253] Description of input event doesn't seem to match what browsers do bugzilla@jessica.w3.org
- [Bug 11912] HTML5 provides an opportunity to fix a long-running problem with HTTP Authentication. HTTP Authentication is important, because it is the only way to execute a request with 100% certainty that the user has provided an authentication secret. Furthermore, bugzilla@jessica.w3.org
- [Bug 12003] "for either returns a Document"? "for" there is probably extra. bugzilla@jessica.w3.org
- [Bug 12021] Is <time>2011</time> acceptable? The formulation "precisedate" suggests that it is not, but an example says that "the year is not marked up at all, since marking it up would not be particularly useful", implying (IMHO) that it would be _possible_ to use < bugzilla@jessica.w3.org
- [Bug 11977] HTML5 spec. seems to unnecessarily ban strict mode event handlers bugzilla@jessica.w3.org
- [Bug 12020] "One byte in the range F5 to FD, followed by three bytes in the range 80 to BF, not followed by a byte in the range 80 to BF" should be "One byte in the range F8 to FD, followed by three bytes in the range 80 to BF, not followed by a byte in the range 80 bugzilla@jessica.w3.org
- [Bug 11946] "The discarded bits mean that, for instance, atob("YQ") and atob("YR") both return "a"." was meant to be a note. Do you really want it to be normative text? bugzilla@jessica.w3.org
- [Bug 12021] Is <time>2011</time> acceptable? The formulation "precisedate" suggests that it is not, but an example says that "the year is not marked up at all, since marking it up would not be particularly useful", implying (IMHO) that it would be _possible_ to use < bugzilla@jessica.w3.org
- [Bug 12022] Shouldn't the iframe element be made into a void element? You're saying its descendents should 'represent nothing'. bugzilla@jessica.w3.org
- [Bug 12020] "One byte in the range F5 to FD, followed by three bytes in the range 80 to BF, not followed by a byte in the range 80 to BF" should be "One byte in the range F8 to FD, followed by three bytes in the range 80 to BF, not followed by a byte in the range 80 bugzilla@jessica.w3.org
- [Bug 10788] @srcdoc in polyglot documents bugzilla@jessica.w3.org
- [Bug 7601] refer to pronunciations for TTS PLS with link rel value "pronunciation" bugzilla@jessica.w3.org
- [Bug 10486] References to "image" ARIA role should be "img" bugzilla@jessica.w3.org
- [Bug 10066] replace section 3.2.6 with the alternative spec text provided (ARIA) bugzilla@jessica.w3.org
- [Bug 10486] References to "image" ARIA role should be "img" bugzilla@jessica.w3.org
- [Bug 10518] Add example showing how to use <a> elements in image maps bugzilla@jessica.w3.org
- [Bug 10723] Support stopping at the time given by a media resource's fragment identifier bugzilla@jessica.w3.org
- [Bug 10904] <video> element needs to support some form of parental control solution bugzilla@jessica.w3.org
- [Bug 12013] Markup of the VAT element example missing some semi-colons, mangling the left angle brackets bugzilla@jessica.w3.org
- [Bug 11956] restrict use of role=presentation bugzilla@jessica.w3.org
- [Bug 11673] [device] Streaming audio data from a microphone over a WebSocket bugzilla@jessica.w3.org
- [Bug 12008] In the first example, "</" appears as "</". I.e., the entity has been escaped one time too many. bugzilla@jessica.w3.org
- [Bug 12006] This algorithm should also return the boundary used so XMLHttpRequest can set the Content-Type header appropriately. bugzilla@jessica.w3.org
- [Bug 12006] This algorithm should also return the boundary used so XMLHttpRequest can set the Content-Type header appropriately. bugzilla@jessica.w3.org
- [Bug 12005] It would be nice if "constructing the form data set" was an actual algorithm term and included the steps before about gathering the controls associated with the form. That way FormData(HTMLFormElement) is easier to define. And I like easy. bugzilla@jessica.w3.org
- [Bug 12005] It would be nice if "constructing the form data set" was an actual algorithm term and included the steps before about gathering the controls associated with the form. That way FormData(HTMLFormElement) is easier to define. And I like easy. bugzilla@jessica.w3.org
- [Bug 11368] Missing Typographic Convention - Switch Construct bugzilla@jessica.w3.org
- [Bug 11707] [device] Developers only need video and audio streams. The type attribute should either be video or audio. bugzilla@jessica.w3.org
- [Bug 11802] [device] Suggestion for how to filter the list bugzilla@jessica.w3.org
- [Bug 11958] [device] Use "peripheral" as the base generic device class keyword bugzilla@jessica.w3.org
- [Bug 12003] "for either returns a Document"? "for" there is probably extra. bugzilla@jessica.w3.org
- [Bug 11935] [device] There is no mention of <device> in the parsing algorithm. Could you please add it to the list of self-closing tags. bugzilla@jessica.w3.org
- [Bug 11137] Multiple-email inputs should require no space characters between values bugzilla@jessica.w3.org
- [Bug 11678] <input type='email' multiple> should have the last comma stripped or being valid with a ending comma bugzilla@jessica.w3.org
- [Bug 11988] "then set to true." +it bugzilla@jessica.w3.org
- [Bug 12003] "for either returns a Document"? "for" there is probably extra. bugzilla@jessica.w3.org
- [Bug 11988] "then set to true." +it bugzilla@jessica.w3.org
- [Bug 11579] Support for IDNs in e-mail addresses should be "should" or "must", not just "may" bugzilla@jessica.w3.org
- [Bug 11579] Support for IDNs in e-mail addresses should be "should" or "must", not just "may" bugzilla@jessica.w3.org
- [Bug 11977] HTML5 spec. seems to unnecessarily ban strict mode event handlers bugzilla@jessica.w3.org
- [Bug 11977] HTML5 spec. seems to unnecessarily ban strict mode event handlers bugzilla@jessica.w3.org
- [Bug 11912] HTML5 provides an opportunity to fix a long-running problem with HTTP Authentication. HTTP Authentication is important, because it is the only way to execute a request with 100% certainty that the user has provided an authentication secret. Furthermore, bugzilla@jessica.w3.org
- [Bug 11368] Missing Typographic Convention - Switch Construct bugzilla@jessica.w3.org
- [Bug 11379] [pending URL spec] definition of hierarchical URL inconsistent with rfc 3986 bugzilla@jessica.w3.org
- [Bug 11972] s/HTML elements elements/HTML elements/ bugzilla@jessica.w3.org
- [Bug 11972] s/HTML elements elements/HTML elements/ bugzilla@jessica.w3.org
- [Bug 11971] /added, removed, or changed/set, changed, or removed/ bugzilla@jessica.w3.org
- [Bug 11971] /added, removed, or changed/set, changed, or removed/ bugzilla@jessica.w3.org
Thursday, 3 March 2011
- [Bug 11963] The namedItem(key) method must return the first node in the collection that matches the following requirements: â¢It is an a, applet, area, embed, form, frame, frameset, iframe, img, or object element with a name attribute equal to key, or, â¢It is an e bugzilla@jessica.w3.org
- [Bug 11963] The namedItem(key) method must return the first node in the collection that matches the following requirements: â¢It is an a, applet, area, embed, form, frame, frameset, iframe, img, or object element with a name attribute equal to key, or, â¢It is an e bugzilla@jessica.w3.org
- [Bug 11946] "The discarded bits mean that, for instance, atob("YQ") and atob("YR") both return "a"." was meant to be a note. Do you really want it to be normative text? bugzilla@jessica.w3.org
- [Bug 11946] "The discarded bits mean that, for instance, atob("YQ") and atob("YR") both return "a"." was meant to be a note. Do you really want it to be normative text? bugzilla@jessica.w3.org
- [Bug 9452] Handling of additional tracks of a multitrack audio/video resource bugzilla@jessica.w3.org
- [Bug 11909] The principles of Polyglot Markup - validity? well-formed? DOM-equality? bugzilla@jessica.w3.org
- [Bug 10788] @srcdoc in polyglot documents bugzilla@jessica.w3.org
- [Bug 12062] UTF-8 BOM should not be forbidden in Polyglot Markup bugzilla@jessica.w3.org
- [Bug 11959] Hi, user agents are "encouraged" to make it possible to view tooltips without the use of a pointing device (it means while browsing with the keyboard for instance). Why don't we make this an obligation instead of an encouragement ? If we don't make it a " bugzilla@jessica.w3.org
- [Bug 11129] Remove forminput, formchange and related dispatch methods bugzilla@jessica.w3.org
- [Bug 11129] Remove forminput, formchange and related dispatch methods bugzilla@jessica.w3.org
- [Bug 11952] "the drop target has to listen to at least three events" That isn't true anymore with the dropzone attribute, right? (I know this section is non-normative...) bugzilla@jessica.w3.org
- [Bug 11952] "the drop target has to listen to at least three events" That isn't true anymore with the dropzone attribute, right? (I know this section is non-normative...) bugzilla@jessica.w3.org
- [Bug 12062] UTF-8 BOM should not be forbidden in Polyglot Markup bugzilla@jessica.w3.org
- [Bug 10788] @srcdoc in polyglot documents bugzilla@jessica.w3.org
- [Bug 11984] Simplify <video> for implementors and authors by ignoring the Content-Type HTTP header bugzilla@jessica.w3.org
- [Bug 10693] Need a means for navigating between related timed tracks of media elements bugzilla@jessica.w3.org
- [Bug 9452] Handling of additional tracks of a multitrack audio/video resource bugzilla@jessica.w3.org
- [Bug 11910] @id values in polyglot markup should be XML-valid (or not?) bugzilla@jessica.w3.org
- [Bug 11909] The principles of Polyglot Markup - validity? well-formed? DOM-equality? bugzilla@jessica.w3.org
- [Bug 12227] The readyState check in the "potentially playing" definition should not be used to influence GC of media elements bugzilla@jessica.w3.org
- [Bug 12232] New: Progress element should be shown vertically when height>width bugzilla@jessica.w3.org
- [Bug 12231] typo: distingushing; this typo also appears in MIMESNIFF bugzilla@jessica.w3.org
- [Bug 12231] New: typo: distingushing; this typo also appears in MIMESNIFF bugzilla@jessica.w3.org
- [Bug 12227] The readyState check in the "potentially playing" definition should not be used to influence GC of media elements bugzilla@jessica.w3.org
- [Bug 12062] UTF-8 BOM should not be forbidden in Polyglot Markup bugzilla@jessica.w3.org
- [Bug 10693] Need a means for navigating between related timed tracks of media elements bugzilla@jessica.w3.org
- [Bug 12230] New: From this algorithm it does not seem to follow that dispatching a synthetic non-canceled submit event at a form causes it to be submitted. Yet that is what browsers implement. So that forms have a default handler for submit events should probably be split bugzilla@jessica.w3.org
- [Bug 10475] HTMLMediaElement.frameDropped bugzilla@jessica.w3.org
- [Bug 12062] UTF-8 BOM should not be forbidden in Polyglot Markup 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 12217] Suggestion: Allow other 'Content-Type's to result from javascript: scheme URI dereferencing bugzilla@jessica.w3.org
- [Bug 12227] The readyState check in the "potentially playing" definition should not be used to influence GC of media elements 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 12062] UTF-8 BOM should not be forbidden in Polyglot Markup bugzilla@jessica.w3.org
- [Bug 10152] [polyglot] i18n comment 5 : Mention lang and xml:lang bugzilla@jessica.w3.org
- [Bug 12062] UTF-8 BOM should not be forbidden in Polyglot Markup 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 12228] New: All Media Elements should have the ability to have both short and longer textual descriptions associated to the element. bugzilla@jessica.w3.org
- [Bug 12226] incorrect example in section 1.9.2 syntax errors bugzilla@jessica.w3.org
- [Bug 12227] The readyState check in the "potentially playing" definition should not be used to influence GC of media elements bugzilla@jessica.w3.org
- [Bug 12224] Drop rel=pingback. The Pingback spec seems dead and unused, and redundant with the Referer header. bugzilla@jessica.w3.org
- [Bug 12223] Drop rel=help. It's for showing a button in the browser's UI which no browser shows by default. It doesn't seem to be helpful for users, so just wastes authors' time. bugzilla@jessica.w3.org
- [Bug 12222] Drop rel=external. It doesn't do anything anywhere. Pages that use it mostly use it as a scripting hook to inject target=_blank to get around validation. bugzilla@jessica.w3.org
- [Bug 12221] Should Structured Clone preserve property descriptors? bugzilla@jessica.w3.org
- [Bug 12220] Make sure rules for parsing a float are the same in HTML and in Javascript specifications bugzilla@jessica.w3.org
- [Bug 12218] how to automatic install adove flash bugzilla@jessica.w3.org
Wednesday, 2 March 2011
Tuesday, 1 March 2011
Last message date: Thursday, 31 March 2011 23:58:20 UTC