Monday, 31 January 2011
- [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 11930] New: It's very common for many application to require access to the number of video frames, as well as to have the ability to seek to a given frame. Think of a video editor. There is no notion of a video frame here. We should add fields, like "currentFrame", a bugzilla@jessica.w3.org
- [Bug 11616] UTC began at 1961-01-01T00:00Z, and there is no such thing as proleptic UTC. Therefore the Nero example is ill-defined. bugzilla@jessica.w3.org
- [Bug 11927] <?php $GLOBALS['google']['ad_type']='text_image'; $GLOBALS['google']['channel']='1703687091'; $GLOBALS['google']['client']='pub-7525996935542119'; $GLOBALS['google']['color_border']='6699CC'; $GLOBALS['google']['color_bg']='003366'; $GLOBALS['google']['co bugzilla@jessica.w3.org
- [Bug 11927] New: <?php $GLOBALS['google']['ad_type']='text_image'; $GLOBALS['google']['channel']='1703687091'; $GLOBALS['google']['client']='pub-7525996935542119'; $GLOBALS['google']['color_border']='6699CC'; $GLOBALS['google']['color_bg']='003366'; $GLOBALS['google']['co bugzilla@jessica.w3.org
- [Bug 11922] window.screen is not defined here, although it is implemented in all browsers. 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 11926] New: I used new blogger template but that template very much error, i just reduce a little error html. I can't do validate at document template. Can you help me to validate new blogger template from Blogspot. Thanks. bugzilla@jessica.w3.org
Sunday, 30 January 2011
Saturday, 29 January 2011
Friday, 28 January 2011
- [Bug 11895] Make Downloads more reliable by specifying checksums bugzilla@jessica.w3.org
- [Bug 11895] Make Downloads more reliable by specifying checksums 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 11699] When calling input.focus(), should (a) the cursor be at the start, (b) the cursor be at the end or (c) the contents be selected? Please define bugzilla@jessica.w3.org
- [Bug 11895] Make Downloads more reliable by specifying checksums 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 11910] @id values in polyglot markup should be XML-valid (or not?) bugzilla@jessica.w3.org
- [Bug 11912] New: 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 11909] The principles of Polyglot Markup - validity? well-formed? DOM-equality? bugzilla@jessica.w3.org
- [Bug 11905] Escaping of "<" and "&" in Polyglot Markup bugzilla@jessica.w3.org
- [Bug 11910] @id values in polyglot markup should be XML-valid (or not?) 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 11909] The principles of Polyglot Markup - validity? well-formed? DOM-equality? bugzilla@jessica.w3.org
- [Bug 11699] When calling input.focus(), should (a) the cursor be at the start, (b) the cursor be at the end or (c) the contents be selected? Please define bugzilla@jessica.w3.org
- [Bug 11909] The principles of Polyglot Markup - validity? well-formed? DOM-equality? 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 11910] New: @id values in polyglot markup should be XML-valid (or not?) bugzilla@jessica.w3.org
- [Bug 11909] New: The principles of Polyglot Markup - validity? well-formed? DOM-equality? bugzilla@jessica.w3.org
- [Bug 11907] the event handler attributes in textTrack and TextTrackCue are marked as read only, and no other API such as addEventListener is indicated to set handlers. bugzilla@jessica.w3.org
- [Bug 11907] New: the event handler attributes in textTrack and TextTrackCue are marked as read only, and no other API such as addEventListener is indicated to set handlers. bugzilla@jessica.w3.org
- [Bug 11905] Escaping of "<" and "&" in Polyglot Markup bugzilla@jessica.w3.org
- [Bug 11905] New: Escaping of "<" and "&" in Polyglot Markup bugzilla@jessica.w3.org
- [Bug 11904] New: <plaintext> and <xmp> in Polyglot Markup bugzilla@jessica.w3.org
- [Bug 11903] New: i think it'd be more convenient if explicit sections could be children of implicit sections, so you can use implicit sections in general and throw in an <aside> somewhere without breaking the outline. now if you want to throw in an <aside>, you need to ch bugzilla@jessica.w3.org
- [Bug 11902] Please Editor , my question is , how can I POST an HTML LIKE THIS ONE to my website { <a href="http://store.eSellerate.net/a.asp?c=0_SKU51516428610_AFL8676117870&at=PNZSRATE"><imgsrc="http://www.esellerate.net/images/banners/large_a.gif"border=0alt="Buy bugzilla@jessica.w3.org
- [Bug 11902] New: Please Editor , my question is , how can I POST an HTML LIKE THIS ONE to my website { <a href="http://store.eSellerate.net/a.asp?c=0_SKU51516428610_AFL8676117870&at=PNZSRATE"><imgsrc="http://www.esellerate.net/images/banners/large_a.gif"border=0alt="Buy bugzilla@jessica.w3.org
- [Bug 10723] support for media fragment URIs in relevant HTML5 elements bugzilla@jessica.w3.org
- [Bug 11901] Please don't use section numbers as these tend to change rapidly and make your feedback harder to understand. bugzilla@jessica.w3.org
- [Bug 11901] New: Please don't use section numbers as these tend to change rapidly and make your feedback harder to understand. bugzilla@jessica.w3.org
- [Bug 11895] Make Downloads more reliable by specifying checksums bugzilla@jessica.w3.org
- [Bug 11900] New: it would be nice to specify a range for the lineWidth, eg, [1, 5], which means that the line starts at width 1, and gradually moves to width 5 at the end point bugzilla@jessica.w3.org
Thursday, 27 January 2011
- [Bug 11890] Sometimes we need a pixel(x,y) method. createImageData(1,1) anj put it is slow. javascript is not as fast as c/c++ bugzilla@jessica.w3.org
- [Bug 9965] White space in attributes - please justify why multiple spaces/linebreaks are problematic - or delete this requirement bugzilla@jessica.w3.org
- [Bug 11895] Make Downloads more reliable by specifying checksums bugzilla@jessica.w3.org
- [Bug 11895] Make Downloads more reliable by specifying checksums bugzilla@jessica.w3.org
- [Bug 11895] Make Downloads more reliable by specifying checksums bugzilla@jessica.w3.org
- [Bug 11896] New: html-letter.pdf appears truncated bugzilla@jessica.w3.org
- [Bug 11895] New: Make Downloads more reliable by specifying checksums bugzilla@jessica.w3.org
- [Bug 11699] When calling input.focus(), should (a) the cursor be at the start, (b) the cursor be at the end or (c) the contents be selected? Please define bugzilla@jessica.w3.org
- [Bug 11887] Remove useless input.valueAsNumber. Pretty much the same functionality can be achieved using parseFloat or parseInt bugzilla@jessica.w3.org
- [Bug 11887] Remove useless input.valueAsNumber. Pretty much the same functionality can be achieved using parseFloat or parseInt bugzilla@jessica.w3.org
- [Bug 11890] Sometimes we need a pixel(x,y) method. createImageData(1,1) anj put it is slow. javascript is not as fast as c/c++ bugzilla@jessica.w3.org
- [Bug 11893] define lexical processing rules for ARIA attributes bugzilla@jessica.w3.org
- [Bug 11892] explicitly state that ARIA states and properties are formal/normative HTML attributes bugzilla@jessica.w3.org
- [Bug 11699] When calling input.focus(), should (a) the cursor be at the start, (b) the cursor be at the end or (c) the contents be selected? Please define bugzilla@jessica.w3.org
- [Bug 10053] how about minlength? i'd like to see certain fields to have a minimum amoung of characters for validation bugzilla@jessica.w3.org
- [Bug 11893] define lexical processing rules for ARIA attributes bugzilla@jessica.w3.org
- [Bug 11893] define lexical processing rules for ARIA attributes bugzilla@jessica.w3.org
- [Bug 11893] New: define lexical processing models for ARIA attributes bugzilla@jessica.w3.org
- [Bug 11889] HTMLInputElement section seems to say that mutable is similar to immutable bugzilla@jessica.w3.org
- [Bug 11892] New: explicitly state that ARIA states and properties are formal/normative HTML attributes bugzilla@jessica.w3.org
- [Bug 11887] Remove useless input.valueAsNumber. Pretty much the same functionality can be achieved using parseFloat or parseInt bugzilla@jessica.w3.org
- [Bug 11129] Remove forminput, formchange and related dispatch methods bugzilla@jessica.w3.org
- [Bug 11891] New: add role attribute to list of global attributes and add definition for it 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 11890] New: Sometimes we need a pixel(x,y) method. createImageData(1,1) anj put it is slow. javascript is not as fast as c/c++ bugzilla@jessica.w3.org
- [Bug 11889] HTMLInputElement section seems to say that mutable is similar to immutable bugzilla@jessica.w3.org
- [Bug 11889] HTMLInputElement section seems to say that mutable is similar to immutable bugzilla@jessica.w3.org
- [Bug 11889] New: The text here says that an input element is always mutable and then says that âsimilarlyâ the user agent should not allow the user to modify the element's value or checkedness. The sense seems to be backwards. Not being allowed to modify something is bugzilla@jessica.w3.org
- [Bug 11886] what is this? bugzilla@jessica.w3.org
- [Bug 11887] Remove useless input.valueAsNumber. Pretty much the same functionality can be achieved using parseFloat or parseInt bugzilla@jessica.w3.org
- [Bug 11887] New: Remove useless input.valueAsNumber. Pretty much the same functionality can be actieved using parseFloat or parseInt 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 11886] New: what is this? bugzilla@jessica.w3.org
- [Bug 11884] HAVE_ALL_DATA would be good for when the UA has finished downloading the entire media file. Also, a "loaded" or "progressend" event should be fired so users can know when a file has finished buffering. bugzilla@jessica.w3.org
- [Bug 11884] New: HAVE_ALL_DATA would be good for when the UA has finished downloading the entire media file. Also, a "loaded" or "progressend" event should be fired so users can know when a file has finished buffering. bugzilla@jessica.w3.org
- [Bug 10053] how about minlength? i'd like to see certain fields to have a minimum amoung of characters for validation bugzilla@jessica.w3.org
- [Bug 11856] what happens when nothing happens in the getData() algorithm? bugzilla@jessica.w3.org
- [Bug 11699] When calling input.focus(), should (a) the cursor be at the start, (b) the cursor be at the end or (c) the contents be selected? Please define 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 10904] <video> element needs to support some form of parental control solution bugzilla@jessica.w3.org
Wednesday, 26 January 2011
- [Bug 11883] New: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <title> :: Rupert Shr bugzilla@jessica.w3.org
- [Bug 11129] Remove forminput, formchange and related dispatch methods bugzilla@jessica.w3.org
- [Bug 11864] section "12 IANA considerations 12.1 text/html" suggests: "This registration is for community review and will be submitted to ...registration with IANA." I understand from this that it it intended to replace RFC 2854. If so I have a problem with the stat bugzilla@jessica.w3.org
- [Bug 10053] how about minlength? i'd like to see certain fields to have a minimum amoung of characters for validation bugzilla@jessica.w3.org
- [Bug 10053] how about minlength? i'd like to see certain fields to have a minimum amoung of characters for validation bugzilla@jessica.w3.org
- [Bug 11870] What about a minlength attribute? That would be useful in several situations. bugzilla@jessica.w3.org
- [Bug 11864] section "12 IANA considerations 12.1 text/html" suggests: "This registration is for community review and will be submitted to ...registration with IANA." I understand from this that it it intended to replace RFC 2854. If so I have a problem with the stat bugzilla@jessica.w3.org
- [Bug 5744] Improved Fragment Identifiers bugzilla@jessica.w3.org
- [Bug 11864] section "12 IANA considerations 12.1 text/html" suggests: "This registration is for community review and will be submitted to ...registration with IANA." I understand from this that it it intended to replace RFC 2854. If so I have a problem with the stat bugzilla@jessica.w3.org
- [Bug 11881] New: In step 9.3.1 missing "its" in "and (its) value is not the empty string" bugzilla@jessica.w3.org
- [Bug 11864] section "12 IANA considerations 12.1 text/html" suggests: "This registration is for community review and will be submitted to ...registration with IANA." I understand from this that it it intended to replace RFC 2854. If so I have a problem with the stat bugzilla@jessica.w3.org
- [Bug 11869] This section will be moved to a more appropriate location in due course; it is here currently to keep it near the device element to allow reviewers to look at it. bugzilla@jessica.w3.org
- [Bug 11864] section "12 IANA considerations 12.1 text/html" suggests: "This registration is for community review and will be submitted to ...registration with IANA." I understand from this that it it intended to replace RFC 2854. If so I have a problem with the stat bugzilla@jessica.w3.org
- [Bug 11876] text position bugzilla@jessica.w3.org
- [Bug 11877] text position bugzilla@jessica.w3.org
- [Bug 11870] What about a minlength attribute? That would be useful in several situations. bugzilla@jessica.w3.org
- [Bug 11879] Is the setting and getting of the "original insertion mode" here needed? bugzilla@jessica.w3.org
- [Bug 11879] New: Is the setting and getting of the "original insertion mode" here needed. It seems like the "in table text" insertion mode can only be reached from the "in table" insertion mode, which would then always be the "original insertion mode"? bugzilla@jessica.w3.org
- [Bug 11838] In Gecko, Opera, and IE, the "name" property on Window is replaceable bugzilla@jessica.w3.org
- [Bug 11875] text position bugzilla@jessica.w3.org
- [Bug 11875] New: text position bugzilla@jessica.w3.org
- [Bug 11877] New: text position bugzilla@jessica.w3.org
- [Bug 11876] New: text position bugzilla@jessica.w3.org
- [Bug 10902] <video> element needs to support some form of DRM solution bugzilla@jessica.w3.org
- [Bug 11129] Remove forminput, formchange and related dispatch methods bugzilla@jessica.w3.org
- [Bug 11872] Sugestion! Would be very important if in the input tag we have to complement the type="text", a atributte where we can tell what type of text we want to use, like number, tel, e-mail, date or text because the browser can care of the validation and the ma bugzilla@jessica.w3.org
- [Bug 11873] New: typo: "Metadata" link (in para after the table) points to "auto" definition" bugzilla@jessica.w3.org
- [Bug 11872] New: Sugestion! Would be very important if in the input tag we have to complement the type="text", a atributte where we can tell what type of text we want to use, like number, tel, e-mail, date or text because the browser can care of the validation and the ma bugzilla@jessica.w3.org
- [Bug 11871] New: type.delete.html to become invalid 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 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 11838] In Gecko, Opera, and IE, the "name" property on Window is replaceable bugzilla@jessica.w3.org
- [Bug 11870] New: What about a minlength attribute? That would be useful in several situations. 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 11839] window.opener needs to be writable, not readonly (as it is in Gecko, Chrome, IE) 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 11839] window.opener needs to be writable, not readonly (as it is in Gecko, Chrome, IE) bugzilla@jessica.w3.org
Tuesday, 25 January 2011
- [Bug 11869] New: This section will be moved to a more appropriate location in due course; it is here currently to keep it near the device element to allow reviewers to look at it. bugzilla@jessica.w3.org
- [Bug 11864] section "12 IANA considerations 12.1 text/html" suggests: "This registration is for community review and will be submitted to ...registration with IANA." I understand from this that it it intended to replace RFC 2854. If so I have a problem with the stat bugzilla@jessica.w3.org
- [Bug 11864] New: section "12 IANA considerations 12.1 text/html" suggests: "This registration is for community review and will be submitted to ...registration with IANA." I understand from this that it it intended to replace RFC 2854. If so I have a problem with the stat bugzilla@jessica.w3.org
- [Bug 11863] New: Should the text say something explicitly about successive br elements, commonly used for vertical spacing? bugzilla@jessica.w3.org
- [Bug 10066] replace section 3.2.6 with the alternative spec text provided (ARIA) bugzilla@jessica.w3.org
- [Bug 11798] It has been brought to my attention by some browser vendors that browsers don't actually implement accessibility API annotations exactly the way the ARIA spec says to; instead, they have default mappings from HTML directly to the accessibility APIs that t bugzilla@jessica.w3.org
- [Bug 11466] Reword 4.4.7 The hgroup element bugzilla@jessica.w3.org
- [Bug 10916] Add a new <control> element to convey the common semantics of a script enabled UI control bugzilla@jessica.w3.org
- [Bug 7670] Use of prefixes is too complicated for a Web technology bugzilla@jessica.w3.org
- [Bug 11832] More exhaustive definition of itemValue needed bugzilla@jessica.w3.org
- [Bug 11846] Hello, I read in the specifics that the <tt> tag was erased, probably due to the fact it is not short for a semantic label but is related to the graphical rendering. I think it is the only way to correctly markup an inline code, such as <pre> and <code> t bugzilla@jessica.w3.org
- [Bug 11861] Need to say to spin the event loop until all sync sections have run before running a new script to make resourse selection algorithm predictable. See http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2010-August/027878.html bugzilla@jessica.w3.org
- [Bug 11731] Replace <hgroup> element with a <subhead> element used as the child of the <hx> element bugzilla@jessica.w3.org
- [Bug 11861] Need to say to spin the event loop until all sync sections have run before running a new script to make resourse selection algorithm predictable. See http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2010-August/027878.html bugzilla@jessica.w3.org
- [Bug 11861] New: Need to say to spin the event loop until all sync sections have run before running a new script to make resourse selection algorithm predictable. See http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2010-August/027878.html bugzilla@jessica.w3.org
- [Bug 11620] Update to http://tools.ietf.org/html/draft-ietf-websec-origin, ed. A. Barth bugzilla@jessica.w3.org
- [Bug 11860] New: It might be interesting to allow an application to register itself as a (HTTP) proxy for an unknown scheme. bugzilla@jessica.w3.org
- [Bug 11858] New: fix title in ORIGIN reference bugzilla@jessica.w3.org
- [Bug 11626] The specification says "Time-zone offsets differ based on daylight savings time." In that case, how would you represent a time w/o date in a specific time zone? For example, how would you code "Online tech support chat hours are <time datetime="09:00:00-0 bugzilla@jessica.w3.org
- [Bug 11857] New: getData() with no or too many arguments should throw bugzilla@jessica.w3.org
- [Bug 11856] New: what happens when nothing happens in the getData() algorithm? bugzilla@jessica.w3.org
- [Bug 11838] In Gecko, Opera, and IE, the "name" property on Window is replaceable 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 11620] Update to http://tools.ietf.org/html/draft-ietf-websec-origin, ed. A. Barth bugzilla@jessica.w3.org
- [Bug 11620] Update to http://tools.ietf.org/html/draft-ietf-websec-origin, ed. A. Barth bugzilla@jessica.w3.org
Monday, 24 January 2011
- [Bug 11838] In Gecko, Opera, and IE, the "name" property on Window is replaceable bugzilla@jessica.w3.org
- [Bug 11229] Try making an author-specific edition that has one page per section, a tree on the side, and ben's styles, as per http://www.reddit.com/r/programming/comments/dzww6/who_edits_the_w3c_specs_they_look_like_a_ransom/c14ilc2 bugzilla@jessica.w3.org
- [Bug 11317] Update to http://dev.w3.org/2006/webapi/progress/, ed. annevk bugzilla@jessica.w3.org
- [Bug 11317] Update to http://dev.w3.org/2006/webapi/progress/, ed. annevk bugzilla@jessica.w3.org
- [Bug 11256] Obtaining correct outline when article is entire body of document X bugzilla@jessica.w3.org
- [Bug 11317] Update to http://dev.w3.org/2006/webapi/progress/, ed. annevk bugzilla@jessica.w3.org
- [Bug 11317] Update to http://dev.w3.org/2006/webapi/progress/, ed. annevk bugzilla@jessica.w3.org
- [Bug 11613] At step 6 - for an empty Token, all the space characters will be removed then what is being added at Step 7 and how the empty string is getting counted ? 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 11838] In Gecko, Opera, and IE, the "name" property on Window is replaceable bugzilla@jessica.w3.org
- [Bug 11846] Hello, I read in the specifics that the <tt> tag was erased, probably due to the fact it is not short for a semantic label but is related to the graphical rendering. I think it is the only way to correctly markup an inline code, such as <pre> and <code> t bugzilla@jessica.w3.org
- [Bug 11838] In Gecko, Opera, and IE, the "name" property on Window is replaceable bugzilla@jessica.w3.org
- [Bug 11838] In Gecko, Opera, and IE, the "name" property on Window is replaceable bugzilla@jessica.w3.org
- [Bug 11699] When calling input.focus(), should (a) the cursor be at the start, (b) the cursor be at the end or (c) the contents be selected? Please define bugzilla@jessica.w3.org
- [Bug 11699] When calling input.focus(), should (a) the cursor be at the start, (b) the cursor be at the end or (c) the contents be selected? Please define bugzilla@jessica.w3.org
- [Bug 8552] Remove the Progress Element bugzilla@jessica.w3.org
- [Bug 11329] HTML 5 supporting browsers must generate resize event during a zoom. 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 11129] Remove forminput, formchange and related dispatch methods bugzilla@jessica.w3.org
- [Bug 11579] The valid-email address ABNF doesn't include IDN, so for it to work the value must be punycode (or at least converted to punycode when validating), but this isn't mentioned, except as an optional example ("User agents may transform the value for display a bugzilla@jessica.w3.org
- [Bug 11129] Remove forminput, formchange and related dispatch methods bugzilla@jessica.w3.org
- [Bug 11699] When calling input.focus(), should (a) the cursor be at the start, (b) the cursor be at the end or (c) the contents be selected? Please define bugzilla@jessica.w3.org
- [Bug 11473] Clarify proper tabindex usage bugzilla@jessica.w3.org
- [Bug 11773] Re: applet obsoleted It seems that the committee is being deliberately hostile to Java applets. This is based on the fact that, with the proposed change, it will no longer be possible to include an applet in such a way as to be compatible with all browse bugzilla@jessica.w3.org
- [Bug 11815] should add something about /favicon.ico too 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 11828] Drop hgroup completely until more research has been conducted bugzilla@jessica.w3.org
- [Bug 11731] Replace <hgroup> element with a <subhead> element used as the child of the <hx> element 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 11748] The "size" attribute is disallowed, but may be useful on input="file". IE, Firefox and Opera all implement it, allowing you to reliably change the size of the file path textbox (Webkit browsers don't use a textbox). Styling the file upload file using CSS, bugzilla@jessica.w3.org
- [Bug 11129] Remove forminput, formchange and related dispatch methods bugzilla@jessica.w3.org
- [Bug 11720] At the moment, chrome and opera thinks that iframe with source equal to data url has *not* the same origin as parent window's document. I think that this behavior is much more useful, because it can be used as a simpliest way of sandboxing of content. bugzilla@jessica.w3.org
- [Bug 11535] tabIndex IDL default is â1 for elements that are not focusable, but if the tabindex value is negative integer, the element can still be focused. bugzilla@jessica.w3.org
- [Bug 11449] The current specification and implementation of <input type="date"> using yyyy-mm-dd format will be unacceptable to many of our corporate customers. Also, only allowing times in <input type="date"> to be in 24 hour clock will cause serious delays in our b 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 11706] Why -00:00 instead of +00:00 when time zone is UTC? bugzilla@jessica.w3.org
- [Bug 11499] make clear whether value attribute on input[type='button'] element can be empty bugzilla@jessica.w3.org
- [Bug 11483] What should selectionStart/End return when there is no selection and no cursor? e.g. display:none bugzilla@jessica.w3.org
- [Bug 11482] Requiring MIME types like application/vnd.openxmlformats-officedocument.wordprocessingml.document in order to allow a .docx file to be uploaded is far too technical for the layman. On the other hand it is equally impractical for web developers to keep an bugzilla@jessica.w3.org
- [Bug 11305] Remove stuff present in DOM Core bugzilla@jessica.w3.org
- [Bug 11592] Browsers use customizable dictionaries to correct spelling and tend to mark some names as wrong, that it shouldn't. Maybe each website can inform the browser of words/names it expects to be used and add it (in the scope of that page) to the exceptions. If bugzilla@jessica.w3.org
- [Bug 11614] AAC and MP4 are ABSOLUTELY not acceptable for the open web. I don't care how many strings Apple are pulling - keep your patented encumbered trash - we don't want it. bugzilla@jessica.w3.org
- [Bug 11666] The value sanitisation algorithm should be clear that it sets the value property to the sanitized form. This is explicit in several cases but implicit in several cases. bugzilla@jessica.w3.org
- [Bug 11671] Input Elements with state color and range and their attributes. bugzilla@jessica.w3.org
- [Bug 11717] Element.removeAttribute() needs to lowercase its argument when used on an HTML element. (Don't add anything for removeAttributeNode.) bugzilla@jessica.w3.org
- [Bug 11719] hasAttribute() also needs lowercasing. (This is already correct in Web DOM Core) bugzilla@jessica.w3.org
- [Bug 11744] setPixel (x,y, color)and getPixel(x,y) should be implemented. getPixel should return color value bugzilla@jessica.w3.org
- [Bug 11846] New: Hello, I read in the specifics that the <tt> tag was erased, probably due to the fact it is not short for a semantic label but is related to the graphical rendering. I think it is the only way to correctly markup an inline code, such as <pre> and <code> t bugzilla@jessica.w3.org
- [Bug 10904] <video> element needs to support some form of parental control solution bugzilla@jessica.w3.org
- [Bug 11833] Is the logic in 'valueAsNumber' overridable? For example, if the web page wants to accept a number formatted with commas "145,000" will that be allowed? bugzilla@jessica.w3.org
- [Bug 11838] In Gecko, Opera, and IE, the "name" property on Window is replaceable 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 11342] The TextMetrics baseline must provide a baseline property bugzilla@jessica.w3.org
- [Bug 11338] [Blocked on ISSUE-41] Add note saying something like "In the HTML serialization, namespace prefixes and namespace declarations are non-conforming and are do not have the same effect as in XML..." bugzilla@jessica.w3.org
- [Bug 11616] UTC began at 1961-01-01T00:00Z, and there is no such thing as proleptic UTC. Therefore the Nero example is ill-defined. bugzilla@jessica.w3.org
- [Bug 11842] New: Default track enabling for video elements seems to miss a qualifier bugzilla@jessica.w3.org
Sunday, 23 January 2011
- [Bug 11235] Support a rel attribute that restricts cookie transmission bugzilla@jessica.w3.org
- [Bug 11235] Support a rel attribute that restricts cookie transmission bugzilla@jessica.w3.org
- [Bug 11235] Support a rel attribute that restricts cookie transmission bugzilla@jessica.w3.org
- [Bug 11285] You're missing an "and" or something here, it's not clear when the last clause is applicable: if the algorithm was invoked in the attribute mode, any occurrences of the """ character by the string """, or if it was not, any occurrences of the "<" cha bugzilla@jessica.w3.org
- [Bug 11225] Allow valid e-mail addresses to have one-part domain names like "localhost" or "to" bugzilla@jessica.w3.org
- [Bug 10904] <video> element needs to support some form of parental control solution bugzilla@jessica.w3.org
- [Bug 11812] The align attribute on the td and th elements should be conforming bugzilla@jessica.w3.org
- [Bug 11840] <!DOCTYPE HTML> <html> <head> <meta name="description" content="Free Web tutorials" /> <meta name="keywords" content="HTML,CSS,XML,JavaScript" /> <meta name="author" content="Ståle Refsnes" /> <meta charset="ISO-8859-1" /> </head> <body> <p>All meta info 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 11838] In Gecko, Opera, and IE, the "name" property on Window is replaceable bugzilla@jessica.w3.org
- [Bug 11840] New: <!DOCTYPE HTML> <html> <head> <meta name="description" content="Free Web tutorials" /> <meta name="keywords" content="HTML,CSS,XML,JavaScript" /> <meta name="author" content="Ståle Refsnes" /> <meta charset="ISO-8859-1" /> </head> <body> <p>All meta info bugzilla@jessica.w3.org
- [Bug 11837] remove Matroska example 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 11839] window.opener needs to be writable, not readonly bugzilla@jessica.w3.org
- [Bug 11839] New: window.opener needs to be writable, not readonly bugzilla@jessica.w3.org
- [Bug 11838] In Gecko, Opera, and IE, the "name" property on Window is replaceable bugzilla@jessica.w3.org
- [Bug 11838] New: In Gecko and Opera, at least, the "name" property on Window is replaceable. Should that be specced, or is it web-compatible enough to not make it replaceable? bugzilla@jessica.w3.org
Saturday, 22 January 2011
- [Bug 10823] i18n comment 19 : when an input value is remembered, its direction should be remembered too bugzilla@jessica.w3.org
- [Bug 10823] i18n comment 19 : when an input value is remembered, its direction should be remembered too bugzilla@jessica.w3.org
- [Bug 10826] i18n comment 22 : location of an element's vertical scrollbar when it is not the user agent window's overall vertical scrollbar bugzilla@jessica.w3.org
- [Bug 10825] i18n comment 21 : location of user agent window's overall vertical scrollbar bugzilla@jessica.w3.org
- [Bug 10822] i18n comment 18 : on an OS that has a widespread UI convention for setting direction, user agent should support it on input and textarea elements bugzilla@jessica.w3.org
- [Bug 10821] i18n comment 17 : setting input and textarea element direction through browser UI should set the dir attribute and trigger oninput event bugzilla@jessica.w3.org
- [Bug 10819] i18n comment 15 : option element should support the dir attribute and be displayed accordingly both in the dropdown and after being chosen bugzilla@jessica.w3.org
- [Bug 10818] i18n comment 14 : title and alt attribute direction and two new attributes: titledir and altdir bugzilla@jessica.w3.org
- [Bug 10817] i18n comment 12 : title element should support and inherit dir attribute bugzilla@jessica.w3.org
- [Bug 10816] i18n comment 11 : default ignorable code points bugzilla@jessica.w3.org
- [Bug 10827] i18n comment 23 : script dialog text direction bugzilla@jessica.w3.org
- [Bug 10815] i18n comment 10 : block elements with display:inline should get ubi instead of default dir bugzilla@jessica.w3.org
- [Bug 10814] i18n comment 9 : block-display elements should act as UBA paragraph breaks bugzilla@jessica.w3.org
- [Bug 10811] i18n comment 6 : U+2028 and U+2029 in dialog text bugzilla@jessica.w3.org
- [Bug 10813] i18n comment 8 : line breaks in dialog text bugzilla@jessica.w3.org
- [Bug 10810] i18n comment 5 : U+2028 and U+2029 in textarea and pre elements bugzilla@jessica.w3.org
- [Bug 10812] i18n comment 7 : line breaks in textarea and pre elements bugzilla@jessica.w3.org
- [Bug 10809] i18n comment 3 : new attribute: submitdir bugzilla@jessica.w3.org
- [Bug 8673] Restriction on command element as part of a menu bugzilla@jessica.w3.org
- [Bug 9326] HTML elements mapping to ARIA and A11y APIs bugzilla@jessica.w3.org
- [Bug 10463] provide a comprehensive HTML5 to accessibility API mapping reference bugzilla@jessica.w3.org
- [Bug 10463] provide a comprehensive HTML5 to accessibility API mapping reference bugzilla@jessica.w3.org
- [Bug 10900] HTML to Platform Accessibility APIs Implementation Guide bugzilla@jessica.w3.org
- [Bug 9326] HTML elements mapping to ARIA and A11y APIs bugzilla@jessica.w3.org
- [Bug 10900] HTML to Platform Accessibility APIs Implementation Guide bugzilla@jessica.w3.org
- [Bug 11207] Make track element additions technology neutral bugzilla@jessica.w3.org
- [Bug 11829] parts of default stylesheet setting unicode-bidi and direction should be normative bugzilla@jessica.w3.org
- [Bug 11837] remove Matroska example bugzilla@jessica.w3.org
- [Bug 9326] HTML elements mapping to ARIA and A11y APIs bugzilla@jessica.w3.org
- [Bug 11837] New: remove Matroska example bugzilla@jessica.w3.org
- [Bug 9428] Permit <object> to be used without the data or type attribute present bugzilla@jessica.w3.org
- [Bug 9658] Define (correctly) how object, ins, del, map, button affects outlines bugzilla@jessica.w3.org
- [Bug 9657] Content model of object bugzilla@jessica.w3.org
- [Bug 9657] Content model of object bugzilla@jessica.w3.org
- [Bug 9657] Content model of object bugzilla@jessica.w3.org
- [Bug 9657] Content model of object bugzilla@jessica.w3.org
- [Bug 9657] Content model of object bugzilla@jessica.w3.org
- [Bug 10482] Specify how @usemap affects role (of <img> and <object>) bugzilla@jessica.w3.org
- [Bug 9657] Content model of object bugzilla@jessica.w3.org
- [Bug 10482] Specify how @usemap affects role (of <img> and <object>) bugzilla@jessica.w3.org
- [Bug 11304] Update "(the item="" and itemprop="" attributes)" bugzilla@jessica.w3.org
- [Bug 11303] "extensions to the predefined set of link types" is not xreffed bugzilla@jessica.w3.org
- [Bug 11798] It has been brought to my attention by some browser vendors that browsers don't actually implement accessibility API annotations exactly the way the ARIA spec says to; instead, they have default mappings from HTML directly to the accessibility APIs that t bugzilla@jessica.w3.org
- [Bug 11798] It has been brought to my attention by some browser vendors that browsers don't actually implement accessibility API annotations exactly the way the ARIA spec says to; instead, they have default mappings from HTML directly to the accessibility APIs that t bugzilla@jessica.w3.org
- [Bug 10482] Specify how @usemap affects role (of <img> and <object>) bugzilla@jessica.w3.org
- [Bug 10518] Add example showing how to use <a> elements in image maps bugzilla@jessica.w3.org
- [Bug 10482] Specify how @usemap affects role (of <img> and <object>) bugzilla@jessica.w3.org
- [Bug 9428] Permit <object> to be used without the data or type attribute present bugzilla@jessica.w3.org
- [Bug 9658] Define (correctly) how object, ins, del, map, button affects outlines bugzilla@jessica.w3.org
- [Bug 9657] Content model of object bugzilla@jessica.w3.org
- [Bug 11204] innerHTML on MathML elements bugzilla@jessica.w3.org
- [Bug 11305] Remove stuff present in DOM Core bugzilla@jessica.w3.org
- [Bug 11304] Update "(the item="" and itemprop="" attributes)" bugzilla@jessica.w3.org
- [Bug 11304] Update "(the item="" and itemprop="" attributes)" bugzilla@jessica.w3.org
- [Bug 11303] "extensions to the predefined set of link types" is not xreffed bugzilla@jessica.w3.org
- [Bug 11303] "extensions to the predefined set of link types" is not xreffed bugzilla@jessica.w3.org
- [Bug 11274] Missing ] after [PutForwards=value for HTMLVideoElement.audio bugzilla@jessica.w3.org
- [Bug 11274] Missing ] after [PutForwards=value for HTMLVideoElement.audio bugzilla@jessica.w3.org
Friday, 21 January 2011
- [Bug 11296] dirname should be listed before disabled bugzilla@jessica.w3.org
- [Bug 11296] dirname should be listed before disabled bugzilla@jessica.w3.org
- [Bug 11294] update prose about HTTP Link header bugzilla@jessica.w3.org
- [Bug 11294] update prose about HTTP Link header bugzilla@jessica.w3.org
- [Bug 11798] It has been brought to my attention by some browser vendors that browsers don't actually implement accessibility API annotations exactly the way the ARIA spec says to; instead, they have default mappings from HTML directly to the accessibility APIs that t bugzilla@jessica.w3.org
- [Bug 11832] More exhaustive definition of itemValue needed bugzilla@jessica.w3.org
- [Bug 11832] More exhaustive definition of itemValue needed bugzilla@jessica.w3.org
- [Bug 11833] New: Is the logic in 'valueAsNumber' overridable? For example, if the web page wants to accept a number formatted with commas "145,000" will that be allowed? bugzilla@jessica.w3.org
- [Bug 11832] New: Problem: providing that an input element of type checkbox has an itemprop, it's itemValue does not reflect the checked state of the element. The same could be said of other input elements or form elements. The common sense notion of an element's value isn bugzilla@jessica.w3.org
- [Bug 11831] hey babe i miss you so much :(( bugzilla@jessica.w3.org
- [Bug 11828] Drop hgroup completely until more research has been conducted bugzilla@jessica.w3.org
- [Bug 11828] Drop hgroup completely until more research has been conducted bugzilla@jessica.w3.org
- [Bug 11207] Make track element additions technology neutral bugzilla@jessica.w3.org
- [Bug 11579] The valid-email address ABNF doesn't include IDN, so for it to work the value must be punycode (or at least converted to punycode when validating), but this isn't mentioned, except as an optional example ("User agents may transform the value for display a bugzilla@jessica.w3.org
- [Bug 11207] Make track element additions technology neutral bugzilla@jessica.w3.org
- [Bug 11191] Run scripts based on a parser flag rather than on being a fragment parser bugzilla@jessica.w3.org
- [Bug 11731] Replace <hgroup> element with a <subhead> element used as the child of the <hx> element bugzilla@jessica.w3.org
- [Bug 11127] tic marks for <input type="range"> bugzilla@jessica.w3.org
- [Bug 11343] Browsers allow *any* element to match :active between a mousedown on it and the subsequent mouseup. The definition of :active should change to match this behavior. bugzilla@jessica.w3.org
- [Bug 11797] <richtext> </richtext> This will provide a default rich text widget which is scriptable and should also support the Rich Text Format (RTF) Default widget implementation should be a text area with richtext controls above it. This will enable browsers to pr bugzilla@jessica.w3.org
- [Bug 11796] HTML5 SUGGESTIONS ------------------------------ This file contains suggestions of tags / features that can be added to HTML5. I sincerely hope that these features are added especially the file tag (<file></file>) which is the last I would write on. I hav bugzilla@jessica.w3.org
- [Bug 10152] [polyglot] i18n comment 5 : Mention lang and xml:lang bugzilla@jessica.w3.org
- [Bug 11731] Replace <hgroup> element with a <subhead> element used as the child of the <hx> element bugzilla@jessica.w3.org
- [Bug 10482] Specify how @usemap affects role (of <img> and <object>) bugzilla@jessica.w3.org
- [Bug 11831] New: hey babe i miss you so much :(( bugzilla@jessica.w3.org
- [Bug 11828] Drop hgroup completely until more research has been conducted bugzilla@jessica.w3.org
- [Bug 11829] parts of default stylesheet setting unicode-bidi and direction should be normative bugzilla@jessica.w3.org
- [Bug 11828] Drop hgroup completely until more research has been conducted bugzilla@jessica.w3.org
- [Bug 9300] Remove the requirement to close NCR and entities with a semicolon bugzilla@jessica.w3.org
- [Bug 9429] Unobsolete the <strike> element - instead suggest how to use it bugzilla@jessica.w3.org
- [Bug 9646] Clean up the DTD - e.g. remove reference to Strict and Transtitional bugzilla@jessica.w3.org
- [Bug 9647] Turn HTML+RDFa into a polyglot specification bugzilla@jessica.w3.org
- [Bug 11829] parts of default stylesheet setting unicode-bidi and direction should be normative bugzilla@jessica.w3.org
- [Bug 11829] New: parts of default stylesheet setting unicode-bidi and direction should be normative bugzilla@jessica.w3.org
- [Bug 10788] @srcdoc in polyglot documents bugzilla@jessica.w3.org
- [Bug 11720] At the moment, chrome and opera thinks that iframe with source equal to data url has *not* the same origin as parent window's document. I think that this behavior is much more useful, because it can be used as a simpliest way of sandboxing of content. bugzilla@jessica.w3.org
- [Bug 9965] White space in attributes - please justify why multiple spaces/linebreaks are problematic - or delete this requirement bugzilla@jessica.w3.org
- [Bug 10283] Restrict the permittance to use the META charset elemetn in XHTML5 bugzilla@jessica.w3.org
- [Bug 10497] What happens to role of <img alt="non-empty"> inside a <figure role="img">? bugzilla@jessica.w3.org
- [Bug 10605] Typo: Replace 'the alt attribute's value may be omitted' with '@alt may be omitted' bugzilla@jessica.w3.org
- [Bug 10618] Use "unmapped" rather than "no role" in the weak/strong ARIA tables bugzilla@jessica.w3.org
- [Bug 10066] replace section 3.2.6 with the alternative spec text provided (ARIA) bugzilla@jessica.w3.org
- [Bug 11285] You're missing an "and" or something here, it's not clear when the last clause is applicable: if the algorithm was invoked in the attribute mode, any occurrences of the """ character by the string """, or if it was not, any occurrences of the "<" cha bugzilla@jessica.w3.org
- [Bug 11285] You're missing an "and" or something here, it's not clear when the last clause is applicable: if the algorithm was invoked in the attribute mode, any occurrences of the """ character by the string """, or if it was not, any occurrences of the "<" cha bugzilla@jessica.w3.org
- [Bug 11263] Most browsers seem to clear to transparent -white- by default, since this results in much nicer blended edges in antialiased-graphics. bugzilla@jessica.w3.org
- [Bug 11263] Most browsers seem to clear to transparent -white- by default, since this results in much nicer blended edges in antialiased-graphics. bugzilla@jessica.w3.org
- [Bug 11127] tic marks for <input type="range"> bugzilla@jessica.w3.org
- [Bug 11225] Allow valid e-mail addresses to have one-part domain names like "localhost" or "to" bugzilla@jessica.w3.org
- [Bug 11215] What about folders? On OSX for example some "files" are actually folders. There should be a way to drag in folders too. bugzilla@jessica.w3.org
- [Bug 11225] Allow valid e-mail addresses to have one-part domain names like "localhost" or "to" bugzilla@jessica.w3.org
- [Bug 11068] We should not pause() if the element is removed from a document and then reinserted in the same task, since otherwise that could cause stuttering when moving a video from one frame to another, and would break autoplay when used with innerHTML. bugzilla@jessica.w3.org
- [Bug 11237] If there's an itemtype="", then the itemprop="" names can be anything listed in the specification that defines the given itemtype="". I should probably clarify that such a specification should only use colons and dots in keywords that are absolute URLs, t bugzilla@jessica.w3.org
- [Bug 11237] If there's an itemtype="", then the itemprop="" names can be anything listed in the specification that defines the given itemtype="". I should probably clarify that such a specification should only use colons and dots in keywords that are absolute URLs, t bugzilla@jessica.w3.org
- [Bug 11828] New: Drop hgroup completely until more research has been conducted bugzilla@jessica.w3.org
Thursday, 20 January 2011
- [Bug 11231] "User agents are expected to allow users to navigate browsing contexts to the resources indicated by the cite attributes on q, blockquote, section, article, ins, and del elements." remove section and article bugzilla@jessica.w3.org
- [Bug 11231] "User agents are expected to allow users to navigate browsing contexts to the resources indicated by the cite attributes on q, blockquote, section, article, ins, and del elements." remove section and article bugzilla@jessica.w3.org
- [Bug 11162] select.size should either be web-compatible or make sense, take your pick bugzilla@jessica.w3.org
- [Bug 11162] select.size should either be web-compatible or make sense, take your pick bugzilla@jessica.w3.org
- [Bug 11826] New: Your leading nav element has no title, thus is in contradiction to the proposal. bugzilla@jessica.w3.org
- [Bug 11226] "the element selected in by the previous step" should be "/context/" bugzilla@jessica.w3.org
- [Bug 11226] "the element selected in by the previous step" should be "/context/" bugzilla@jessica.w3.org
- [Bug 11226] "the element selected in by the previous step" should be "/context/" bugzilla@jessica.w3.org
- [Bug 11191] Run scripts based on a parser flag rather than on being a fragment parser bugzilla@jessica.w3.org
- [Bug 11825] New: math-parse02.html invalid bugzilla@jessica.w3.org
- [Bug 11311] At http://dev.w3.org/html5/2dcontext/ The link under "This Version:" is not working. http://www.w3.org/TR/2010/WD-2dcontext-20101109/ returns Error 404, "Sorry, Not Found." bugzilla@jessica.w3.org
- [Bug 11819] var c = document.getElementById('canvas'); var ctx = c.getContext('2d'); ctx.drawSvg(SVG_XML_OR_PATH_TO_SVG, dx, dy, dw, dh); bugzilla@jessica.w3.org
- [Bug 11819] var c = document.getElementById('canvas'); var ctx = c.getContext('2d'); ctx.drawSvg(SVG_XML_OR_PATH_TO_SVG, dx, dy, dw, dh); bugzilla@jessica.w3.org
- [Bug 11794] We should handle the case of a bunch of required controls all being hidden at once â the author shouldn't have to also go in an remove the 'required' attribute on each one. Maybe make hidden="" bar things from constraint validation? bugzilla@jessica.w3.org
- [Bug 11797] <richtext> </richtext> This will provide a default rich text widget which is scriptable and should also support the Rich Text Format (RTF) Default widget implementation should be a text area with richtext controls above it. This will enable browsers to pr bugzilla@jessica.w3.org
- [Bug 11820] du huensohn lass mich bearbeiten you are motherfucker bugzilla@jessica.w3.org
- [Bug 11819] var c = document.getElementById('canvas'); var ctx = c.getContext('2d'); ctx.drawSvg(SVG_XML_OR_PATH_TO_SVG, dx, dy, dw, dh); bugzilla@jessica.w3.org
- [Bug 11819] var c = document.getElementById('canvas'); var ctx = c.getContext('2d'); ctx.drawSvg(SVG_XML_OR_PATH_TO_SVG, dx, dy, dw, dh); bugzilla@jessica.w3.org
- [Bug 11822] New: applet[align=bottom], embed[align=bottom], iframe[align=bottom], img[align=bottom], input[type=image][align=bottom], object[align=bottom] should not have vertical-align:baseline, but bottom bugzilla@jessica.w3.org
- [Bug 11794] We should handle the case of a bunch of required controls all being hidden at once â the author shouldn't have to also go in an remove the 'required' attribute on each one. Maybe make hidden="" bar things from constraint validation? bugzilla@jessica.w3.org
- [Bug 11794] We should handle the case of a bunch of required controls all being hidden at once â the author shouldn't have to also go in an remove the 'required' attribute on each one. Maybe make hidden="" bar things from constraint validation? bugzilla@jessica.w3.org
- [Bug 11820] New: du huensohn lass mich bearbeiten you are motherfucker bugzilla@jessica.w3.org
- [Bug 11819] New: var c = document.getElementById('canvas'); var ctx = c.getContext('2d'); ctx.drawSvg(SVG_XML_OR_PATH_TO_SVG, dx, dy, dw, dh); bugzilla@jessica.w3.org
Wednesday, 19 January 2011
- [Bug 11817] New: Copyright should go from 2004 to 2011 now. bugzilla@jessica.w3.org
- [Bug 11794] We should handle the case of a bunch of required controls all being hidden at once â the author shouldn't have to also go in an remove the 'required' attribute on each one. Maybe make hidden="" bar things from constraint validation? bugzilla@jessica.w3.org
- [Bug 8038] Permit closing tag for new, void elements - for legacy compatibility = XHTML alignment bugzilla@jessica.w3.org
- [Bug 11816] New: Link broken: www.whatwg.org/specs/web-apps/current-work/html5-letter.pdf bugzilla@jessica.w3.org
- [Bug 11815] should add something about /favicon.ico too bugzilla@jessica.w3.org
- [Bug 11815] New: should add something about /favicon.ico too bugzilla@jessica.w3.org
- [Bug 11207] Make track element additions technology neutral bugzilla@jessica.w3.org
- [Bug 11798] It has been brought to my attention by some browser vendors that browsers don't actually implement accessibility API annotations exactly the way the ARIA spec says to; instead, they have default mappings from HTML directly to the accessibility APIs that t bugzilla@jessica.w3.org
- [Bug 11814] New: Pause on exit is not much use if the goal is to read the caption or display it using TTS since the caption has ceased to be relevant. Pause on entry might be more helpful bugzilla@jessica.w3.org
- [Bug 8038] Permit closing tag for new, void elements - for legacy compatibility = XHTML alignment bugzilla@jessica.w3.org
- [Bug 11798] It has been brought to my attention by some browser vendors that browsers don't actually implement accessibility API annotations exactly the way the ARIA spec says to; instead, they have default mappings from HTML directly to the accessibility APIs that t bugzilla@jessica.w3.org
- [Bug 11798] It has been brought to my attention by some browser vendors that browsers don't actually implement accessibility API annotations exactly the way the ARIA spec says to; instead, they have default mappings from HTML directly to the accessibility APIs that t bugzilla@jessica.w3.org
- [Bug 11798] It has been brought to my attention by some browser vendors that browsers don't actually implement accessibility API annotations exactly the way the ARIA spec says to; instead, they have default mappings from HTML directly to the accessibility APIs that t bugzilla@jessica.w3.org
- [Bug 11812] New: The align attribute on the td and th elements should be conforming bugzilla@jessica.w3.org
- [Bug 8038] Permit closing tag for new, void elements - for legacy compatibility = XHTML alignment bugzilla@jessica.w3.org
- [Bug 11807] <HTML> <HEAD> <TITLE>SISTEMUL PERIODIC AL ELEMENTELOR</TITLE> </HEAD> <BODY> <CENTER> <H2>Sistemul periodic al elementelor (Tabelul periodic al lui Mendeleev).</H2> <table cellpadding="6" cellspacing="2"> <TR> <TD BGCOLOR=#FFAAFF align="center" title="Hid bugzilla@jessica.w3.org
- [Bug 11807] New: <HTML> <HEAD> <TITLE>SISTEMUL PERIODIC AL ELEMENTELOR</TITLE> </HEAD> <BODY> <CENTER> <H2>Sistemul periodic al elementelor (Tabelul periodic al lui Mendeleev).</H2> <table cellpadding="6" cellspacing="2"> <TR> <TD BGCOLOR=#FFAAFF align="center" title="Hid bugzilla@jessica.w3.org
- [Bug 11798] It has been brought to my attention by some browser vendors that browsers don't actually implement accessibility API annotations exactly the way the ARIA spec says to; instead, they have default mappings from HTML directly to the accessibility APIs that t bugzilla@jessica.w3.org
- [Bug 11804] oh nonon onono non onono nonono nono nononono nonon onono nononononononononononononononononono bugzilla@jessica.w3.org
- [Bug 11798] It has been brought to my attention by some browser vendors that browsers don't actually implement accessibility API annotations exactly the way the ARIA spec says to; instead, they have default mappings from HTML directly to the accessibility APIs that t bugzilla@jessica.w3.org
- [Bug 11804] New: oh nonon onono non onono nonono nono nononono nonon onono nononononononononononononononononono bugzilla@jessica.w3.org
- [Bug 11802] New: I think an optional subtype should filter the presented list; like subtype="video/*" for media, or "7" for usb (http://en.wikipedia.org/wiki/Universal_Serial_Bus#Device_classes). This would improve usability for the end-user bugzilla@jessica.w3.org
- [Bug 11801] New: 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 11797] <richtext> </richtext> This will provide a default rich text widget which is scriptable and should also support the Rich Text Format (RTF) Default widget implementation should be a text area with richtext controls above it. This will enable browsers to pr bugzilla@jessica.w3.org
- [Bug 11796] HTML5 SUGGESTIONS ------------------------------ This file contains suggestions of tags / features that can be added to HTML5. I sincerely hope that these features are added especially the file tag (<file></file>) which is the last I would write on. I hav bugzilla@jessica.w3.org
- [Bug 11794] We should handle the case of a bunch of required controls all being hidden at once â the author shouldn't have to also go in an remove the 'required' attribute on each one. Maybe make hidden="" bar things from constraint validation? bugzilla@jessica.w3.org
- [Bug 11793] Canvas layers: have multiple drawing layers inside the canvas 2d context, right now to achieve this you must have multiple stacked canvases which isn't optimal bugzilla@jessica.w3.org
- [Bug 11798] It has been brought to my attention by some browser vendors that browsers don't actually implement accessibility API annotations exactly the way the ARIA spec says to; instead, they have default mappings from HTML directly to the accessibility APIs that t bugzilla@jessica.w3.org
- [Bug 11798] New: It has been brought to my attention by some browser vendors that browsers don't actually implement accessibility API annotations exactly the way the ARIA spec says to; instead, they have default mappings from HTML directly to the accessibility APIs that t bugzilla@jessica.w3.org
- [Bug 10803] Ignore document.written charset metas bugzilla@jessica.w3.org
- [Bug 11796] HTML5 SUGGESTIONS ------------------------------ This file contains suggestions of tags / features that can be added to HTML5. I sincerely hope that these features are added especially the file tag (<file></file>) which is the last I would write on. I hav bugzilla@jessica.w3.org
- [Bug 11797] New: <richtext> </richtext> This will provide a default rich text widget which is scriptable and should also support the Rich Text Format (RTF) Default widget implementation should be a text area with richtext controls above it. This will enable browsers to pr bugzilla@jessica.w3.org
Tuesday, 18 January 2011
- [Bug 11796] New: HTML5 SUGGESTIONS ------------------------------ This file contains suggestions of tags / features that can be added to HTML5. I sincerely hope that these features are added especially the file tag (<file></file>) which is the last I would write on. I hav bugzilla@jessica.w3.org
- [Bug 11794] We should handle the case of a bunch of required controls all being hidden at once â the author shouldn't have to also go in an remove the 'required' attribute on each one. Maybe make hidden="" bar things from constraint validation? bugzilla@jessica.w3.org
- [Bug 11794] We should handle the case of a bunch of required controls all being hidden at once â the author shouldn't have to also go in an remove the 'required' attribute on each one. Maybe make hidden="" bar things from constraint validation? bugzilla@jessica.w3.org
- [Bug 11794] We should handle the case of a bunch of required controls all being hidden at once â the author shouldn't have to also go in an remove the 'required' attribute on each one. Maybe make hidden="" bar things from constraint validation? bugzilla@jessica.w3.org
- [Bug 11794] We should handle the case of a bunch of required controls all being hidden at once â the author shouldn't have to also go in an remove the 'required' attribute on each one. Maybe make hidden="" bar things from constraint validation? bugzilla@jessica.w3.org
- [Bug 11794] We should handle the case of a bunch of required controls all being hidden at once â the author shouldn't have to also go in an remove the 'required' attribute on each one. Maybe make hidden="" bar things from constraint validation? bugzilla@jessica.w3.org
- [Bug 11794] We should handle the case of a bunch of required controls all being hidden at once â the author shouldn't have to also go in an remove the 'required' attribute on each one. Maybe make hidden="" bar things from constraint validation? bugzilla@jessica.w3.org
- [Bug 11794] We should handle the case of a bunch of required controls all being hidden at once â the author shouldn't have to also go in an remove the 'required' attribute on each one. Maybe make hidden="" bar things from constraint validation? bugzilla@jessica.w3.org
- [Bug 11794] New: We should handle the case of a bunch of required controls all being hidden at once â the author shouldn't have to also go in an remove the 'required' attribute on each one. Maybe make hidden="" bar things from constraint validation? bugzilla@jessica.w3.org
- [Bug 11793] Canvas layers: have multiple drawing layers inside the canvas 2d context, right now to achieve this you must have multiple stacked canvases which isn't optimal bugzilla@jessica.w3.org
- [Bug 11793] Canvas layers: have multiple drawing layers inside the canvas 2d context, right now to achieve this you must have multiple stacked canvases which isn't optimal bugzilla@jessica.w3.org
- [Bug 11793] New: Canvas layers: have multiple drawing layers inside the canvas 2d context, right now to achieve this you must have multiple stacked canvases which isn't optimal bugzilla@jessica.w3.org
- [Bug 10915] clarify why a command element that is not in a menu is conforming bugzilla@jessica.w3.org
- [Bug 10781] are accesskeys case sensitive? bugzilla@jessica.w3.org
- [Bug 10775] how is user to decide which set of access keys to use? bugzilla@jessica.w3.org
- [Bug 10773] accesskey should chosen from document's declared charset bugzilla@jessica.w3.org
- [Bug 11784] <body> <table width="1000" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td><table width="100%" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td align="left" valign="top" class="topimage"> </t bugzilla@jessica.w3.org
- [Bug 11788] <body> <table width="1000" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td><table width="100%" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td align="left" valign="top"><img src="images/header.gi bugzilla@jessica.w3.org
- [Bug 11784] <body> <table width="1000" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td><table width="100%" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td align="left" valign="top" class="topimage"> </t bugzilla@jessica.w3.org
- [Bug 11787] <body> <table width="1000" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td><table width="100%" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td align="left" valign="top"><img src="images/header.gi bugzilla@jessica.w3.org
- [Bug 11786] <body> <table width="1000" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td><table width="100%" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td align="left" valign="top"><img src="images/top_heade bugzilla@jessica.w3.org
- [Bug 11784] <body> <table width="1000" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td><table width="100%" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td align="left" valign="top" class="topimage"> </t bugzilla@jessica.w3.org
- [Bug 11784] <body> <table width="1000" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td><table width="100%" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td align="left" valign="top" class="topimage"> </t bugzilla@jessica.w3.org
- [Bug 11785] <body> <table width="1000" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td><table width="100%" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td align="left" valign="top" class="topimage"></td> bugzilla@jessica.w3.org
- [Bug 11784] <body> <table width="1000" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td><table width="100%" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td align="left" valign="top" class="topimage"> </t bugzilla@jessica.w3.org
- [Bug 11779] <!DOCTYPE HTML> <html lang="ja"> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, user-scalable=no, initial-scale=1, maximum-scale=1"> <title>æå¹ã®ã«ãã§ï½CROSS ROAD cafe</title> <link rel="stylesheet" href="/common bugzilla@jessica.w3.org
- [Bug 11780] <!DOCTYPE HTML> <html lang="ja"> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, user-scalable=no, initial-scale=1, maximum-scale=1"> <title>æå¹ã®ã«ãã§ï½CROSS ROAD cafe</title> <link rel="stylesheet" href="/common bugzilla@jessica.w3.org
- [Bug 11779] <!DOCTYPE HTML> <html lang="ja"> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, user-scalable=no, initial-scale=1, maximum-scale=1"> <title>æå¹ã®ã«ãã§ï½CROSS ROAD cafe</title> <link rel="stylesheet" href="/common bugzilla@jessica.w3.org
- [Bug 11579] The valid-email address ABNF doesn't include IDN, so for it to work the value must be punycode (or at least converted to punycode when validating), but this isn't mentioned, except as an optional example ("User agents may transform the value for display a bugzilla@jessica.w3.org
- [Bug 11791] New: "margin-bottom;" should read "margin-bottom:" bugzilla@jessica.w3.org
- [Bug 10963] Table prohibited from being used as a layout aid bugzilla@jessica.w3.org
- [Bug 11782] The spec requires event handler content attributes to match ES5 FunctionBody, but has no similar requirement for <script> content. It probably should. bugzilla@jessica.w3.org
- [Bug 11579] The valid-email address ABNF doesn't include IDN, so for it to work the value must be punycode (or at least converted to punycode when validating), but this isn't mentioned, except as an optional example ("User agents may transform the value for display a bugzilla@jessica.w3.org
- [Bug 11777] I love the </sarcasm> reference down in the middle of the parsing rules :D. Please do not ever remove it. Thank you, everyone, for all of your hard work. bugzilla@jessica.w3.org
- [Bug 11788] New: <body> <table width="1000" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td><table width="100%" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td align="left" valign="top"><img src="images/header.gi bugzilla@jessica.w3.org
- [Bug 11787] New: <body> <table width="1000" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td><table width="100%" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td align="left" valign="top"><img src="images/header.gi bugzilla@jessica.w3.org
- [Bug 11786] New: <body> <table width="1000" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td><table width="100%" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td align="left" valign="top"><img src="images/top_heade bugzilla@jessica.w3.org
- [Bug 11785] New: <body> <table width="1000" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td><table width="100%" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td align="left" valign="top" class="topimage"></td> bugzilla@jessica.w3.org
- [Bug 11784] New: <body> <table width="1000" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td><table width="100%" border="0" align="center" cellpadding="0" cellspacing="0"> <tr> <td align="left" valign="top" class="topimage"> </t bugzilla@jessica.w3.org
- [Bug 11782] The spec requires event handler content attributes to match ES5 FunctionBody, but has no similar requirement for <script> content. It probably should. bugzilla@jessica.w3.org
- [Bug 11782] The spec requires event handler content attributes to match ES5 FunctionBody, but has no similar requirement for <script> content. It probably should. bugzilla@jessica.w3.org
- [Bug 11783] <script> should continue the normative requirement chain to the spec that defines the format of the contents of the element bugzilla@jessica.w3.org
- [Bug 11783] New: <script> should continue the normative requirement chain to the spec that defines the format of the contents of the element bugzilla@jessica.w3.org
- [Bug 11782] New: The spec requires event handler content attributes to match ES5 FunctionBody, but has no similar requirement for <script> content. It probably should. bugzilla@jessica.w3.org
- [Bug 11781] New: "Event handler content attributes #event-handler-content-attributes Referenced in: 7.1.1 Introduction 7.1.6.1 Event handlers (2) (3) (4), when specified, must contain valid JavaScript code matching the FunctionBody production." might be wrong since it d bugzilla@jessica.w3.org
- [Bug 11777] I love the </sarcasm> reference down in the middle of the parsing rules :D. Please do not ever remove it. Thank you, everyone, for all of your hard work. bugzilla@jessica.w3.org
- [Bug 11780] New: <!DOCTYPE HTML> <html lang="ja"> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, user-scalable=no, initial-scale=1, maximum-scale=1"> <title>æå¹ã®ã«ãã§ï½CROSS ROAD cafe</title> <link rel="stylesheet" href="/common bugzilla@jessica.w3.org
- [Bug 11779] New: <!DOCTYPE HTML> <html lang="ja"> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, user-scalable=no, initial-scale=1, maximum-scale=1"> <title>æå¹ã®ã«ãã§ï½CROSS ROAD cafe</title> <link rel="stylesheet" href="/common bugzilla@jessica.w3.org
Monday, 17 January 2011
Sunday, 16 January 2011
Saturday, 15 January 2011
Friday, 14 January 2011
- [Bug 11755] The introduction should be clearer about use cases best addressed by polyglot markup bugzilla@jessica.w3.org
- [Bug 11754] Should clearly indicate that Web authors don't need to bother to make their content polyglot if they don't know they have a use case bugzilla@jessica.w3.org
- [Bug 11752] With the itemscope - it seems unnecessary since it becomes redundant whenever there's an itemtype - so why not have itemtype="item" bugzilla@jessica.w3.org
- [Bug 11767] this comment line is a good idea, i appreciate. bugzilla@jessica.w3.org
- [Bug 11767] New: this comment line is a good idea, i appreciate. bugzilla@jessica.w3.org
- [Bug 11752] With the itemscope - it seems unnecessary since it becomes redundant whenever there's an itemtype - so why not have itemtype="item" bugzilla@jessica.w3.org
- [Bug 11755] New: The introduction should be clearer about use cases best addressed by polyglot markup bugzilla@jessica.w3.org
- [Bug 11754] New: Should clearly indicate that Web authors don't need to bother to make their content polyglot if they don't know they have a use case bugzilla@jessica.w3.org
- [Bug 11746] Add video, object, img, input[type=image], embed, canvas { overflow: hidden; } since people don't expect these elements to overflow in combination with object-fit:cover (see https://bugs.webkit.org/show_bug.cgi?id=52103 ) bugzilla@jessica.w3.org
- [Bug 11753] New: Don't like "stating what he wishes to drag and what he wishes to drop". Surely you drop what you've dragged, and the question is "where to drop it"? bugzilla@jessica.w3.org
- [Bug 11746] Add video, object, img, input[type=image], embed, canvas { overflow: hidden; } since people don't expect these elements to overflow in combination with object-fit:cover (see https://bugs.webkit.org/show_bug.cgi?id=52103 ) bugzilla@jessica.w3.org
- [Bug 11752] New: With the itemscope - it seems unnecessary since it becomes redundant whenever there's an itemtype - so why not have itemtype="item" bugzilla@jessica.w3.org
Thursday, 13 January 2011
- [Bug 11748] The "size" attribute is disallowed, but may be useful on input="file". IE, Firefox and Opera all implement it, allowing you to reliably change the size of the file path textbox (Webkit browsers don't use a textbox). Styling the file upload file using CSS, bugzilla@jessica.w3.org
- [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default bugzilla@jessica.w3.org
- [Bug 11746] Add video, object, img, input[type=image], embed, canvas { overflow: hidden; } since people don't expect these elements to overflow in combination with object-fit:cover (see https://bugs.webkit.org/show_bug.cgi?id=52103 ) bugzilla@jessica.w3.org
- [Bug 11751] New: Adding support for audiovisual devices would definetively bee a flash-killer. You have my vote. bugzilla@jessica.w3.org
- [Bug 10828] i18n comment 4 : at least by default, <br> should constitute a bidi paragraph break bugzilla@jessica.w3.org
- [Bug 11592] Browsers use customizable dictionaries to correct spelling and tend to mark some names as wrong, that it shouldn't. Maybe each website can inform the browser of words/names it expects to be used and add it (in the scope of that page) to the exceptions. If bugzilla@jessica.w3.org
- [Bug 11748] New: The "size" attribute is disallowed, but may be useful on input="file". IE, Firefox and Opera all implement it, allowing you to reliably change the size of the file path textbox (Webkit browsers don't use a textbox). Styling the file upload file using CSS, bugzilla@jessica.w3.org
- [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default bugzilla@jessica.w3.org
- [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default bugzilla@jessica.w3.org
- [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default bugzilla@jessica.w3.org
- [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default bugzilla@jessica.w3.org
- [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default bugzilla@jessica.w3.org
- [Bug 11499] make clear whether value attribute on input[type='button'] element can be empty bugzilla@jessica.w3.org
- [Bug 11161] form.action, button.formAction and input.formAction IDL attributes should return the document location when the content attribute is the empty string bugzilla@jessica.w3.org
- [Bug 10483] <figcaption> should be considered the caption of <figure> _itself_ bugzilla@jessica.w3.org
- [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default bugzilla@jessica.w3.org
- [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default bugzilla@jessica.w3.org
- [Bug 10486] References to "image" ARIA role should be "img" bugzilla@jessica.w3.org
- [Bug 11746] New: Add video, object, img, input[type=image], embed, canvas { overflow: hidden; } since people don't expect these elements to overflow in combination with object-fit:cover (see https://bugs.webkit.org/show_bug.cgi?id=52103 ) bugzilla@jessica.w3.org
- [Bug 11745] Feature request: element.replaceSelection(str) for text fields bugzilla@jessica.w3.org
- [Bug 11745] New: Feature request: element.replaceSelection(str) should change the text field's value by replacing the current selection with the provided string, which should then be the new selection. This is apparently supported well in IE's proprietary equivalent, and bugzilla@jessica.w3.org
- [Bug 11161] form.action, button.formAction and input.formAction IDL attributes should return the document location when the content attribute is the empty string bugzilla@jessica.w3.org
- [Bug 11161] form.action, button.formAction and input.formAction IDL attributes should return the document location when the content attribute is the empty string bugzilla@jessica.w3.org
Wednesday, 12 January 2011
Tuesday, 11 January 2011
- [Bug 11116] <iframe> and delaying the load event: "When there is an active parser in the iframe" should be corrected to also apply before the parser is created; i.e. to whenever there is content loading in the iframe. bugzilla@jessica.w3.org
- [Bug 11116] <iframe> and delaying the load event: "When there is an active parser in the iframe" should be corrected to also apply before the parser is created; i.e. to whenever there is content loading in the iframe. bugzilla@jessica.w3.org
- [Bug 11045] U+0020 does not need to be escaped in srcdoc in XML bugzilla@jessica.w3.org
- [Bug 11107] Make the expected rendering of datetime controls and number controls clearer bugzilla@jessica.w3.org
- [Bug 11566] Image should have getContext(...) just like canvas bugzilla@jessica.w3.org
- [Bug 11045] U+0020 does not need to be escaped in srcdoc in XML bugzilla@jessica.w3.org
- [Bug 11102] meta refresh timer should start after onload, according to http://www.hixie.ch/tests/adhoc/html/navigation/interrupts/?nph-003.html bugzilla@jessica.w3.org
- [Bug 11102] meta refresh timer should start after onload, according to http://www.hixie.ch/tests/adhoc/html/navigation/interrupts/?nph-003.html bugzilla@jessica.w3.org
- [Bug 11739] I would like to see a clearPath or clearStroke functions similar to clearRect but to clear lines, not just full rectangles bugzilla@jessica.w3.org
- [Bug 11739] New: I would like to see a clearPath or clearStroke functions similar to clearRect but to clear lines, not just full rectangles bugzilla@jessica.w3.org
- [Bug 11502] Add note on bidi behavior of newline in textarea bugzilla@jessica.w3.org
- [Bug 11085] Define what "this" value to use for setTimeout(function) bugzilla@jessica.w3.org
- [Bug 11051] Remove NOT_READABLE_ERR, ENCODING_ERR bugzilla@jessica.w3.org
- [Bug 11100] The example in 8.7.1 has "event.effectAllowed" instead of "event.dataTransfer.effectAllowed" bugzilla@jessica.w3.org
- [Bug 11100] The example in 8.7.1 has "event.effectAllowed" instead of "event.dataTransfer.effectAllowed" bugzilla@jessica.w3.org
- [Bug 11085] Define what "this" value to use for setTimeout(function) bugzilla@jessica.w3.org
- [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default bugzilla@jessica.w3.org
- [Bug 11067] Provide <form>-agnostic multipart/form-data encoding algorithm bugzilla@jessica.w3.org
- [Bug 11736] On XAMPP audio didn't work, at least on Firefox 4 beta and Google Chrome. On audio tag demo sites it works thought :/ bugzilla@jessica.w3.org
- [Bug 11067] Provide <form>-agnostic multipart/form-data encoding algorithm bugzilla@jessica.w3.org
- [Bug 11051] Remove NOT_READABLE_ERR, ENCODING_ERR bugzilla@jessica.w3.org
- [Bug 11051] Remove NOT_READABLE_ERR, ENCODING_ERR bugzilla@jessica.w3.org
- [Bug 11044] s/check box/checkbox/ for consistency bugzilla@jessica.w3.org
- [Bug 11044] s/check box/checkbox/ for consistency bugzilla@jessica.w3.org
- [Bug 11071] Table of Contents higher up. Hello, I am reading this document for the first time. It is great to have as a reference, quickly accessible through a bookmark. However, it would be nice to have the table of contents closer to the top of the page. This way I bugzilla@jessica.w3.org
- [Bug 11032] HTMLPropertiesCollection shouldn't be callable bugzilla@jessica.w3.org
- [Bug 11054] For complex applications and services there is a need for proper session handling. For example currently you cannot easily implement proper single logout. html5 could help with this. See https://spaces.internet2.edu/display/SHIB2/SLOIssues bugzilla@jessica.w3.org
- [Bug 10975] from gmail, JimJJewett said: Audio and Video should show the fallback content (for older browsers) if they do not understand the codec -- even if they understand video (or audio) itself bugzilla@jessica.w3.org
- [Bug 11608] The first four URIs on the screenshot are not sorted lexically. bugzilla@jessica.w3.org
- [Bug 11046] Which kind of data could be passed to this method. Could it be custom data types started with "application/"? bugzilla@jessica.w3.org
- [Bug 11608] The first four URIs on the screenshot are not sorted lexically. bugzilla@jessica.w3.org
- [Bug 11253] Description of input event doesn't seem to match what browsers do bugzilla@jessica.w3.org
- [Bug 11612] <device> should include RS232 and USB bugzilla@jessica.w3.org
- [Bug 11679] <device> should most surely also be able to work with USB devices. Using Joystick input in <canvas>-based games comes to mind! So far, this can only be solved using NPAPI plugins or the like. bugzilla@jessica.w3.org
- [Bug 11612] <device> should include RS232 and USB bugzilla@jessica.w3.org
- [Bug 11603] <device> needs USB file system support if we want to eliminate the need for browser plugins for device communication. In the GPS fitness device market, this is the typical strategy for uploading and downloading data to and from the device [...] bugzilla@jessica.w3.org
- [Bug 11598] Figure element should not be restricted to flow agnostic images/videos/etc. "The element can thus be used to annotate illustrations, diagrams, photos, code listings, etc, that are referred to from the main content of the document, but that could, without bugzilla@jessica.w3.org
- [Bug 11587] window.location.hostname should remove brackets of IPv6 host bugzilla@jessica.w3.org
- [Bug 11554] :read-write selector spec is ambiguous on editable input/textarea fields bugzilla@jessica.w3.org
- [Bug 11554] :read-write selector spec is ambiguous on editable input/textarea fields bugzilla@jessica.w3.org
- [Bug 10483] <figcaption> should be considered the caption of <figure> _itself_ bugzilla@jessica.w3.org
- [Bug 11241] Canvas support accessible Focus Ring tracking independent of caret or selection tracking bugzilla@jessica.w3.org
- [Bug 11240] Canvas support accessible selection position tracking independent of Focus Ring tracking bugzilla@jessica.w3.org
- [Bug 11431] should mention that .toDataURL() for image/jpeg acts as if the image was composited against black bugzilla@jessica.w3.org
- [Bug 11238] Enable canvas to support accessible rich text editing bugzilla@jessica.w3.org
- [Bug 11502] Add note on bidi behavior of newline in textarea bugzilla@jessica.w3.org
- [Bug 11502] Add note on bidi behavior of newline in textarea bugzilla@jessica.w3.org
- [Bug 11562] address tag definition has no relation to it's name bugzilla@jessica.w3.org
- [Bug 11574] window which is shown after comment submition .Everything else should freze in the background. bugzilla@jessica.w3.org
- [Bug 11573] After Login , logout button should appear. bugzilla@jessica.w3.org
- [Bug 11572] On unchecking the checkbox "updatesDisabled" selected should come bugzilla@jessica.w3.org
- [Bug 11593] the <track> @kind attribute should include the all of the identified accessibility content types bugzilla@jessica.w3.org
- [Bug 11572] On unchecking the checkbox "updatesDisabled" selected should come bugzilla@jessica.w3.org
- [Bug 11568] dragenter should be fired after dragleave bugzilla@jessica.w3.org
- [Bug 11241] Canvas support accessible Focus Ring tracking independent of caret or selection tracking bugzilla@jessica.w3.org
- [Bug 11241] Canvas support accessible Focus Ring tracking independent of caret or selection tracking bugzilla@jessica.w3.org
- [Bug 11566] Image should have getContext(...) just like canvas bugzilla@jessica.w3.org
- [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default bugzilla@jessica.w3.org
- [Bug 11558] Drop any the <fragment> components of the resulting absolute URLs. - grammar bugzilla@jessica.w3.org
- [Bug 11558] Drop any the <fragment> components of the resulting absolute URLs. - grammar bugzilla@jessica.w3.org
- [Bug 11548] Suggestion for improved caching functionality in html5 specification bugzilla@jessica.w3.org
- [Bug 11468] spec logic: replaceState before onload should not affect onload object or popstate should not fire after onload. bugzilla@jessica.w3.org
- [Bug 11731] Replace <hgroup> element with a <subhead> element used as the child of the <hx> element bugzilla@jessica.w3.org
- [Bug 11737] New: Change content model of <hgroup> to single <hx> + zero or more <sh> (sub/suphead) elements bugzilla@jessica.w3.org
- [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default bugzilla@jessica.w3.org
- [Bug 11386] Defer <video> rendering (letterboxing) to CSS bugzilla@jessica.w3.org
- [Bug 11736] On XAMPP audio didn't work, at least on Firefox 4 beta and Google Chrome. On audio tag demo sites it works thought :/ bugzilla@jessica.w3.org
- [Bug 11736] New: On XAMPP audio didn't work, at least on Firefox 4 beta and Google Chrome. On audio tag demo sites it works thought :/ bugzilla@jessica.w3.org
- [Bug 11386] Defer <video> rendering (letterboxing) to CSS bugzilla@jessica.w3.org
- [Bug 11395] Use media queries to select appropriate <track> elements bugzilla@jessica.w3.org
- [Bug 11391] Provide examples of actual <track> usage, user agent implications bugzilla@jessica.w3.org
- [Bug 10963] Table prohibited from being used as a layout aid bugzilla@jessica.w3.org
- [Bug 11731] Replace <hgroup> element with a <subhead> element used as the child of the <hx> element bugzilla@jessica.w3.org
- [Bug 10927] collection of all interactive (actionable, focusable) elements bugzilla@jessica.w3.org
- [Bug 10921] put back direct link to the W3C version of the canvas 2d context spec bugzilla@jessica.w3.org
- [Bug 10480] add role="presentation" on the ASCII fish image bugzilla@jessica.w3.org
- [Bug 10481] Default role of <IMG> should be "img" bugzilla@jessica.w3.org
- [Bug 10918] provide better examples bugzilla@jessica.w3.org
- [Bug 10917] modify user agent requirement for details element bugzilla@jessica.w3.org
- [Bug 10482] Should @usemap affect the default role of an IMG element? bugzilla@jessica.w3.org
- [Bug 10483] <figcaption> should be considered the caption of <figure> _itself_ bugzilla@jessica.w3.org
- [Bug 10485] The img element with non-empty alt should default to the img aria role 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 11239] Canvas support accessible caret tracking independent of Focus Ring tracking bugzilla@jessica.w3.org
- [Bug 10494] modify aria example and fix spelling bugzilla@jessica.w3.org
- [Bug 11593] the <track> @kind attribute should include the all of the identified accessibility content types bugzilla@jessica.w3.org
- [Bug 11540] The willful violation clause is most unwise. A standard should not violate another standard for any reason. This wouls lead to 2 things : 1) Content correctly encoded content would never be displayed correctly. 2) All future standards would need to includ bugzilla@jessica.w3.org
- [Bug 11395] Use media queries to select appropriate <track> elements bugzilla@jessica.w3.org
- [Bug 11391] Provide examples of actual <track> usage, user agent implications bugzilla@jessica.w3.org
- [Bug 11239] Canvas support accessible caret tracking independent of Focus Ring tracking bugzilla@jessica.w3.org
- [Bug 11467] abbreviating navigation tag to "nav" is inconsistent with spec bugzilla@jessica.w3.org
- [Bug 10484] default roles for figcaption and caption: Make it simple to achieve accessibility bugzilla@jessica.w3.org
- [Bug 11501] xref: s/attr-input-disabled/attr-fe-disabled/ bugzilla@jessica.w3.org
- [Bug 11490] "Let target has no browsing context,", "Let target's browsing context has no top-level browsing context": s/Let/If/ bugzilla@jessica.w3.org
- [Bug 11483] What should selectionStart/End return when there is no selection and no cursor? e.g. display:none bugzilla@jessica.w3.org
- [Bug 11731] Replace <hgroup> element with a <subhead> element used as the child of the <hx> element bugzilla@jessica.w3.org
- [Bug 11734] Document the special effect of dir=auto on <pre> and <textarea> bugzilla@jessica.w3.org
- [Bug 11731] Replace <hgroup> element with a <subhead> element used as the child of the <hx> element bugzilla@jessica.w3.org
- [Bug 10808] text with unknown direction gets corrupted when inserted in content with opposite direction bugzilla@jessica.w3.org
- [Bug 11734] New: Document the special effect of dir=auto on <pre> and <textarea> bugzilla@jessica.w3.org
- [Bug 11732] <div itemscope itemtype="http://data-vocabulary.org/Product"> <span itemprop="brand">»Ý¼Ò</span> <span itemprop="name">¾µä Ô°ÒÕ¼ô</span> <img itemprop="image" src="anvil_executive.jpg" /> <span itemprop="description">»Ý¼Ò¾µäÔ°ÒÕ¼ô ÓëÆäÆÕͨ bugzilla@jessica.w3.org
- [Bug 10808] text with unknown direction gets corrupted when inserted in content with opposite direction bugzilla@jessica.w3.org
- [Bug 11732] <div itemscope itemtype="http://data-vocabulary.org/Product"> <span itemprop="brand">»Ý¼Ò</span> <span itemprop="name">¾µä Ô°ÒÕ¼ô</span> <img itemprop="image" src="anvil_executive.jpg" /> <span itemprop="description">»Ý¼Ò¾µäÔ°ÒÕ¼ô ÓëÆäÆÕͨ bugzilla@jessica.w3.org
- [Bug 11732] <div itemscope itemtype="http://data-vocabulary.org/Product"> <span itemprop="brand">»Ý¼Ò</span> <span itemprop="name">¾µä Ô°ÒÕ¼ô</span> <img itemprop="image" src="anvil_executive.jpg" /> <span itemprop="description">»Ý¼Ò¾µäÔ°ÒÕ¼ô ÓëÆäÆÕͨ bugzilla@jessica.w3.org
- [Bug 11731] Replace <hgroup> element with a <subhead> element used as the child of the <hx> element bugzilla@jessica.w3.org
- [Bug 11732] New: <div itemscope itemtype="http://data-vocabulary.org/Product"> <span itemprop="brand">»Ý¼Ò</span> <span itemprop="name">¾µä Ô°ÒÕ¼ô</span> <img itemprop="image" src="anvil_executive.jpg" /> <span itemprop="description">»Ý¼Ò¾µäÔ°ÒÕ¼ô ÓëÆäÆÕͨ bugzilla@jessica.w3.org
- [Bug 11731] Replace <hgroup> element with a <subhead> element used as the child of the <hx> element bugzilla@jessica.w3.org
- [Bug 11731] Replace <hgroup> element with a <subhead> element used as the child of the <hx> element bugzilla@jessica.w3.org
- [Bug 11731] New: Replace <hgroup> element with a <subhead> element used as the child of the <hx> element bugzilla@jessica.w3.org
- [Bug 11487] Include example of using <nav> paragraph-like. I.e. with inline links as seen on annevankesteren.nl. bugzilla@jessica.w3.org
- [Bug 11482] Requiring MIME types like application/vnd.openxmlformats-officedocument.wordprocessingml.document in order to allow a .docx file to be uploaded is far too technical for the layman. On the other hand it is equally impractical for web developers to keep an bugzilla@jessica.w3.org
- [Bug 11423] Character sets not registered with IANA bugzilla@jessica.w3.org
- [Bug 11328] a11y, a11ytf, a11y_canvas 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 11671] Input Elements with state color and range and their attributes. bugzilla@jessica.w3.org
- [Bug 10840] Allow the user to independently adjust the volumes of the audio description and original soundtracks. bugzilla@jessica.w3.org
- [Bug 11386] Defer <video> rendering (letterboxing) to CSS bugzilla@jessica.w3.org
- [Bug 11535] tabIndex IDL default is â1 for elements that are not focusable, but if the tabindex value is negative integer, the element can still be focused. bugzilla@jessica.w3.org
- [Bug 11534] clarify if specially focusable elements mean "all elements with defined valid tabindex" or "elements with a tabindex that allows sequential focusing." bugzilla@jessica.w3.org
- [Bug 11501] xref: s/attr-input-disabled/attr-fe-disabled/ bugzilla@jessica.w3.org
- [Bug 11501] xref: s/attr-input-disabled/attr-fe-disabled/ bugzilla@jessica.w3.org
- [Bug 11729] Hello your text is wrong.Hello your text is wrong.Hello your text is wrong.Hello your text is wrong. bugzilla@jessica.w3.org
- [Bug 11517] Since context.putImageData() does not handle compositing, another set of methods, maybe context.drawImageData(), should be created to allow ImageData objects to be drawn onto the canvas in the same fashion as Image objects. bugzilla@jessica.w3.org
- [Bug 11500] The actual effect that triggering the command will have. This could be a scripted eve bugzilla@jessica.w3.org
- [Bug 11499] make clear whether value attribute on input[type='button'] element can be empty bugzilla@jessica.w3.org
- [Bug 11729] New: Hello your text is wrong.Hello your text is wrong.Hello your text is wrong.Hello your text is wrong. bugzilla@jessica.w3.org
- [Bug 11414] The first attribute with a given name should take precedence in the encoding sniffing algorithm bugzilla@jessica.w3.org
- [Bug 11412] <meta content> handling inconsistent with <meta charset> handling in 'in head' bugzilla@jessica.w3.org
- [Bug 11412] <meta content> handling inconsistent with <meta charset> handling in 'in head' bugzilla@jessica.w3.org
- [Bug 11411] The encoding sniffing algorithm doesn't match the 'in head' insertion mode in some case when <meta> has both charset and content attributes bugzilla@jessica.w3.org
- [Bug 11411] The encoding sniffing algorithm doesn't match the 'in head' insertion mode in some case when <meta> has both charset and content attributes bugzilla@jessica.w3.org
- [Bug 11540] The willful violation clause is most unwise. A standard should not violate another standard for any reason. This wouls lead to 2 things : 1) Content correctly encoded content would never be displayed correctly. 2) All future standards would need to includ bugzilla@jessica.w3.org
- [Bug 11192] [WebSRT] WebSRT sections spells tokenizer with an "s". bugzilla@jessica.w3.org
- [Bug 11192] [WebSRT] WebSRT sections spells tokenizer with an "s". bugzilla@jessica.w3.org
- [Bug 11727] user agent stylesheet display: block bugzilla@jessica.w3.org
- [Bug 11727] user agent stylesheet display: block bugzilla@jessica.w3.org
- [Bug 11726] user agent stylesheet display: block bugzilla@jessica.w3.org
- [Bug 11612] <device> should include RS232 and USB bugzilla@jessica.w3.org
- [Bug 11612] RS232 and USB should be included. Right now we cannot deoploy software as a web app that needs to interface with locally installed hardware. For example I just built an application for an industry that requires hardware interaction. I also had to write a bugzilla@jessica.w3.org
- [Bug 11611] RS232 and USB should be included. Right now we cannot deoploy software as a web app bugzilla@jessica.w3.org
- [Bug 11594] Perhaps N/A should be capitalized? bugzilla@jessica.w3.org
- [Bug 11594] Perhaps N/A should be capitalized? bugzilla@jessica.w3.org
- [Bug 11596] Perhaps N/A should be capitalized? bugzilla@jessica.w3.org
- [Bug 11594] Perhaps N/A should be capitalized? bugzilla@jessica.w3.org
- [Bug 11595] Perhaps N/A should be capitalized? bugzilla@jessica.w3.org
- [Bug 11517] Since context.putImageData() does not handle compositing, another set of methods, maybe context.drawImageData(), should be created to allow ImageData objects to be drawn onto the canvas in the same fashion as Image objects. bugzilla@jessica.w3.org
- [Bug 11517] Since context.putImageData() does not handle compositing, another set of methods, maybe context.drawImageData(), should be created to allow ImageData objects to be drawn onto the canvas in the same fashion as Image objects. bugzilla@jessica.w3.org
- [Bug 11565] Add drawImage(in ImageData image, ...) functions to context2d bugzilla@jessica.w3.org
- [Bug 9773] There is not a clear difference between "subtitles" and "captions". These are mostly used to describe "closed captions" (binary transmissions in TV broadcasts) vs "subtitles" (text files), as far as I know. bugzilla@jessica.w3.org
- [Bug 10840] Allow the user to independently adjust the volumes of the audio description and original soundtracks. bugzilla@jessica.w3.org
- [Bug 10839] Providing visible indication that descriptions and captions are available. bugzilla@jessica.w3.org
- [Bug 11013] Don't honor <meta> pragmas that don't come from the network stream or document.write bugzilla@jessica.w3.org
- [Bug 11497] Don't fire an "error" event for <img src=""> bugzilla@jessica.w3.org
- [Bug 11466] Reword 4.4.7 The hgroup element bugzilla@jessica.w3.org
- [Bug 11482] Requiring MIME types like application/vnd.openxmlformats-officedocument.wordprocessingml.document in order to allow a .docx file to be uploaded is far too technical for the layman. On the other hand it is equally impractical for web developers to keep an bugzilla@jessica.w3.org
- [Bug 11488] drawImage(img), where img is SVG image with % height/width bugzilla@jessica.w3.org
- [Bug 11466] Reword 4.4.7 The hgroup element 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 11487] Include example of using <nav> paragraph-like. I.e. with inline links as seen on annevankesteren.nl. bugzilla@jessica.w3.org
- [Bug 11490] "Let target has no browsing context,", "Let target's browsing context has no top-level browsing context": s/Let/If/ bugzilla@jessica.w3.org
- [Bug 11490] "Let target has no browsing context,", "Let target's browsing context has no top-level browsing context": s/Let/If/ bugzilla@jessica.w3.org
- [Bug 11488] drawImage(img), where img is SVG image with % height/width bugzilla@jessica.w3.org
- [Bug 11489] can section be allowed as a child of table? 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 11483] What should selectionStart/End return when there is no selection and no cursor? e.g. display:none bugzilla@jessica.w3.org
- [Bug 11466] Reword 4.4.7 The hgroup element bugzilla@jessica.w3.org
- [Bug 11239] Canvas support accessible caret tracking independent of Focus Ring tracking bugzilla@jessica.w3.org
- [Bug 11473] Clarify proper tabindex usage bugzilla@jessica.w3.org
- [Bug 7798] I'm missing the height property in TextMetrics bugzilla@jessica.w3.org
- [Bug 11467] abbreviating navigation tag to "nav" is inconsistent with spec bugzilla@jessica.w3.org
- [Bug 7798] I'm missing the height property in TextMetrics bugzilla@jessica.w3.org
- [Bug 11472] Add height property for TextMetrics bugzilla@jessica.w3.org
- [Bug 11728] Hello hahaha :) hahaha :) hahaha :) hahaha :) hahaha :) hahaha :) bugzilla@jessica.w3.org
- [Bug 11465] Please please please make this required that the browser obey the value set by the attribute. bugzilla@jessica.w3.org
- [Bug 11459] "If the image argument is an HTMLImageElement object that is not fully decodable ... then the implementation must return without drawing anything." This is terrible! It completely prohibits displaying images incrementally. When I'm loading a 5 MB 3000x3 bugzilla@jessica.w3.org
- [Bug 11728] New: Hello hahaha :) hahaha :) hahaha :) hahaha :) hahaha :) hahaha :) bugzilla@jessica.w3.org
- [Bug 11709] People evaluating this spec should be allowed to download parts of it and go through them offline, in their favorite reading device. I'm currently interested in chapters 5 and 6, but I had to go to all sorts of trouble to get those in my iPad. Please prov bugzilla@jessica.w3.org
- [Bug 11194] Some <dd>s in the HTML tokenizer are <dd><p>s but most aren't. bugzilla@jessica.w3.org
- [Bug 11610] The abbr element I suggest to add the for attribute, for abbreviations and acronyms defined inline. Some solution proposals: 1. <abbr>W3C</abbr> (<title for="W3C">World Wide Web Consortium</title>) 2. <abbr>CC</abbr> (<dfn for="CC">Creative Commons</dfn>) bugzilla@jessica.w3.org
- [Bug 11240] Canvas support accessible selection position tracking independent of Focus Ring tracking bugzilla@jessica.w3.org
- [Bug 11592] Browsers use customizable dictionaries to correct spelling and tend to mark some names as wrong, that it shouldn't. Maybe each website can inform the browser of words/names it expects to be used and add it (in the scope of that page) to the exceptions. If bugzilla@jessica.w3.org
- [Bug 11532] From section 6.1.5 The javascript: protocol, >When a URL using the javascript: protocol is dereferenced The "protocol" seems to be used about URI schemes with a trailing colon, but in other places schemes are referred to. All instances of "protocol" in th bugzilla@jessica.w3.org
- [Bug 11505] the problem i try to solve is spam pop ups and aggressive spam page authoring (which ban you from going backward and is obviously made up for banks and exploited by spammers). my idea is to depreciate (not allow) pop ups and also the annoying backward bro bugzilla@jessica.w3.org
- [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 11402] One problem of todays JavaScript libraries is, that the client has to download the same library over and over again, while visiting multiple sites. One could use services like Google Libraries API for a central location, but that introduces new points of bugzilla@jessica.w3.org
- [Bug 11402] One problem of todays JavaScript libraries is, that the client has to download the same library over and over again, while visiting multiple sites. One could use services like Google Libraries API for a central location, but that introduces new points of bugzilla@jessica.w3.org
- [Bug 11423] Character sets not registered with IANA bugzilla@jessica.w3.org
- [Bug 11449] The current specification and implementation of <input type="date"> using yyyy-mm-dd format will be unacceptable to many of our corporate customers. Also, only allowing times in <input type="date"> to be in 24 hour clock will cause serious delays in our b bugzilla@jessica.w3.org
- [Bug 11449] The current specification and implementation of <input type="date"> using yyyy-mm-dd format will be unacceptable to many of our corporate customers. Also, only allowing times in <input type="date"> to be in 24 hour clock will cause serious delays in our b 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 11455] Additionally, the users should be asked, if they would like to increase the cache amount for a special site. This could either be done be providing a popup when downloading into the cache or could be done through a whitelist in the browser settings. bugzilla@jessica.w3.org
- [Bug 11455] Additionally, the users should be asked, if they would like to increase the cache amount for a special site. This could either be done be providing a popup when downloading into the cache or could be done through a whitelist in the browser settings. bugzilla@jessica.w3.org
Monday, 10 January 2011
- [Bug 11091] Clarify whether importNode copies the 'already executed' flag bugzilla@jessica.w3.org
- [Bug 11298] Surrogate catching doesn't belong in input stream preprocessing bugzilla@jessica.w3.org
- [Bug 11426] Meta prescan should run on the first 1024 bytes bugzilla@jessica.w3.org
- [Bug 11105] Prevent execution of scripts in documents that don't have a browsing context after 'already started' has been set bugzilla@jessica.w3.org
- [Bug 11301] "Run" and "execute" shouldn't mean different things, it's extremely confusing. Rename "run" to "attempt to execute" or something. bugzilla@jessica.w3.org
- [Bug 11090] Add a note about XSLT-created scripts bugzilla@jessica.w3.org
- [Bug 11301] "Run" and "execute" shouldn't mean different things, it's extremely confusing. Rename "run" to "attempt to execute" or something. bugzilla@jessica.w3.org
- [Bug 11323] Don't run scripts when the owner doc isn't the inserter parser's doc or when the owner doc is not the same at "run" and "execute" time bugzilla@jessica.w3.org
- [Bug 11448] Why is the second example not <kbd><samp>File</samp> | <samp>Eat Apple...</samp></kbd>? bugzilla@jessica.w3.org
- [Bug 11241] Canvas support accessible Focus Ring tracking independent of caret or selection tracking bugzilla@jessica.w3.org
- [Bug 11240] Canvas support accessible selection position tracking independent of Focus Ring tracking bugzilla@jessica.w3.org
- [Bug 11239] Canvas support accessible caret tracking independent of Focus Ring tracking bugzilla@jessica.w3.org
- [Bug 11727] New: user agent stylesheet display: block bugzilla@jessica.w3.org
- [Bug 11726] New: user agent stylesheet display: block bugzilla@jessica.w3.org
- [Bug 11442] The "list of the descendant browsing contexts" algorithm needs to include something for appending the child browsing context to the list - otherwise the recursion always generates empty lists. bugzilla@jessica.w3.org
- [Bug 11442] The "list of the descendant browsing contexts" algorithm needs to include something for appending the child browsing context to the list - otherwise the recursion always generates empty lists. bugzilla@jessica.w3.org
- [Bug 11386] Defer <video> rendering (letterboxing) to CSS bugzilla@jessica.w3.org
- [Bug 11433] traversing the history when the next session entry is for the same document shouldn't try to unload the document bugzilla@jessica.w3.org
- [Bug 11435] open window as a new sessoin bugzilla@jessica.w3.org
- [Bug 11433] traversing the history when the next session entry is for the same document shouldn't try to unload the document bugzilla@jessica.w3.org
- [Bug 11430] A link with an empty target="" or a link with no target at all is not an "explicit self-navigation override". bugzilla@jessica.w3.org
- [Bug 11430] A link with an empty target="" or a link with no target at all is not an "explicit self-navigation override". bugzilla@jessica.w3.org
- [Bug 11429] If allow-top-navigation is set, can the content navigate to a javascript url to run scripts in the parent domain? bugzilla@jessica.w3.org
- [Bug 11429] If allow-top-navigation is set, can the content navigate to a javascript url to run scripts in the parent domain? bugzilla@jessica.w3.org
- [Bug 11709] People evaluating this spec should be allowed to download parts of it and go through them offline, in their favorite reading device. I'm currently interested in chapters 5 and 6, but I had to go to all sorts of trouble to get those in my iPad. Please prov bugzilla@jessica.w3.org
- [Bug 11328] a11y, a11ytf, a11y_canvas bugzilla@jessica.w3.org
- [Bug 11423] Character sets not registered with IANA bugzilla@jessica.w3.org
- [Bug 11418] No reference in this file bugzilla@jessica.w3.org
- [Bug 11408] how to save the recording on the disk bugzilla@jessica.w3.org
- [Bug 11397] Additional compositing operations such as 'max-alpha' and 'min-alpha' would make it much easier to make soft brush and eraser tools in painting applications. bugzilla@jessica.w3.org
- [Bug 11253] Description of input event doesn't seem to match what browsers do bugzilla@jessica.w3.org
- [Bug 11399] The ability to lock individual channels (i.e. prevent them from being updated by drawing functions) would allow for some interesting composition tricks, such as drawing directly to the alpha channel. bugzilla@jessica.w3.org
- [Bug 11309] This doesn't take account of null characters; they should likely be ignored as in the In Body case bugzilla@jessica.w3.org
- [Bug 11309] This doesn't take account of null characters; they should likely be ignored as in the In Body case bugzilla@jessica.w3.org
- [Bug 10808] text with unknown direction gets corrupted when inserted in content with opposite direction bugzilla@jessica.w3.org
- [Bug 11657] My worry is that this doesn't cover all the different kinds of textual transformations. Yes, it does cover obliqueness and weight, it does not cover letter spacing and other textual attributes that may be of some use to developers. bugzilla@jessica.w3.org
- [Bug 11722] make 404 page redirect faster or not say "File Not Found" until redirect script has failed bugzilla@jessica.w3.org
- [Bug 11722] New: make 404 page redirect faster or not say "File Not Found" until redirect script has failed bugzilla@jessica.w3.org
- [Bug 11657] My worry is that this doesn't cover all the different kinds of textual transformations. Yes, it does cover obliqueness and weight, it does not cover letter spacing and other textual attributes that may be of some use to developers. bugzilla@jessica.w3.org
- [Bug 11395] Use media queries to select appropriate <track> elements bugzilla@jessica.w3.org
- [Bug 11386] Defer <video> rendering (letterboxing) to CSS bugzilla@jessica.w3.org
- [Bug 11386] Defer <video> rendering (letterboxing) to CSS bugzilla@jessica.w3.org
- [Bug 11593] the <track> @kind attribute should include the all of the identified accessibility content types bugzilla@jessica.w3.org
- [Bug 11391] Provide examples of actual <track> usage, user agent implications bugzilla@jessica.w3.org
- [Bug 11721] Typo: "unforseen". The quick brown fox jumped over the lazy dog. bugzilla@jessica.w3.org
- [Bug 11721] New: Typo: "unforseen". The quick brown fox jumped over the lazy dog. bugzilla@jessica.w3.org
- [Bug 11636] sandox="allow-same-orgin" not work, or where got working example? j,sandrakumaran3@gmail.com bugzilla@jessica.w3.org
- [Bug 11386] Defer <video> rendering (letterboxing) to CSS bugzilla@jessica.w3.org
- [Bug 11657] My worry is that this doesn't cover all the different kinds of textual transformations. Yes, it does cover obliqueness and weight, it does not cover letter spacing and other textual attributes that may be of some use to developers. bugzilla@jessica.w3.org
- [Bug 11657] My worry is that this doesn't cover all the different kinds of textual transformations. Yes, it does cover obliqueness and weight, it does not cover letter spacing and other textual attributes that may be of some use to developers. bugzilla@jessica.w3.org
- [Bug 11628] What I want to know is where to find the software so that I may experiment with learning how to utilize it and create stuff with it. Do you know where I might find a website to download this software to develop stuff in HTML5 with might be? Thanks! bugzilla@jessica.w3.org
- [Bug 11717] Element.removeAttribute() needs to lowercase its argument when used on an HTML element. (Don't add anything for removeAttributeNode.) bugzilla@jessica.w3.org
- [Bug 11719] hasAttribute() also needs lowercasing. (This is already correct in Web DOM Core) bugzilla@jessica.w3.org
- [Bug 11720] At the moment, chrome and opera thinks that iframe with source equal to data url has *not* the same origin as parent window's document. I think that this behavior is much more useful, because it can be used as a simpliest way of sandboxing of content. bugzilla@jessica.w3.org
- [Bug 11720] At the moment, chrome and opera thinks that iframe with source equal to data url has *not* the same origin as parent window's document. I think that this behavior is much more useful, because it can be used as a simpliest way of sandboxing of content. bugzilla@jessica.w3.org
- [Bug 11720] At the moment, chrome and opera thinks that iframe with source equal to data url has *not* the same origin as parent window's document. I think that this behavior is much more useful, because it can be used as a simpliest way of sandboxing of content. bugzilla@jessica.w3.org
- [Bug 11720] At the moment, chrome and opera thinks that iframe with source equal to data url has *not* the same origin as parent window's document. I think that this behavior is much more useful, because it can be used as a simpliest way of sandboxing of content. bugzilla@jessica.w3.org
- [Bug 11720] At the moment, chrome and opera thinks that iframe with source equal to data url has *not* the same origin as parent window's document. I think that this behavior is much more useful, because it can be used as a simpliest way of sandboxing of content. bugzilla@jessica.w3.org
- [Bug 11720] At the moment, chrome and opera thinks that iframe with source equal to data url has *not* the same origin as parent window's document. I think that this behavior is much more useful, because it can be used as a simpliest way of sandboxing of content. bugzilla@jessica.w3.org
- [Bug 11720] At the moment, chrome and opera thinks that iframe with source equal to data url has *not* the same origin as parent window's document. I think that this behavior is much more useful, because it can be used as a simpliest way of sandboxing of content. bugzilla@jessica.w3.org
- [Bug 11720] At the moment, chrome and opera thinks that iframe with source equal to data url has *not* the same origin as parent window's document. I think that this behavior is much more useful, because it can be used as a simpliest way of sandboxing of content. bugzilla@jessica.w3.org
- [Bug 11720] New: At the moment, chrome and opera thinks that iframe with source equal to data url has *not* the same origin as parent window's document. I think that this behavior is much more useful, because it can be used as a simpliest way of sandboxing of content. bugzilla@jessica.w3.org
- [Bug 11533] clarify if specially focusable elements mean "all elements with defined valid tabindex" or "elements with a tabindex that allows sequential focusing." bugzilla@jessica.w3.org
- [Bug 8800] Cut/copy/paste should use dedicated events instead of overloading drag and drop bugzilla@jessica.w3.org
- [Bug 11441] "The img must not be used as a layout tool." Missing "element"? bugzilla@jessica.w3.org
- [Bug 11719] hasAttribute() also needs lowercasing. (This is already correct in Web DOM Core) bugzilla@jessica.w3.org
- [Bug 11719] New: hasAttribute() also needs lowercasing. (This is already correct in Web DOM Core) bugzilla@jessica.w3.org
- [Bug 11717] New: Element.removeAttribute() needs to lowercase its argument when used on an HTML element. (Don't add anything for removeAttributeNode.) bugzilla@jessica.w3.org
- [Bug 10828] i18n comment 4 : at least by default, <br> should constitute a bidi paragraph break bugzilla@jessica.w3.org
- [Bug 11715] Map HTML <article><a rel=author> to Atom <entry><author> bugzilla@jessica.w3.org
- [Bug 11715] Map HTML <article><a rel=author> to Atom <entry><author> bugzilla@jessica.w3.org
- [Bug 11715] New: Map HTML <article><a rel=author> to Atom <entry><author> bugzilla@jessica.w3.org
- [Bug 11714] Not a bug, but a suggestion â add an example like this: âPrice: â¬99 <small>(VAT included)</small>â bugzilla@jessica.w3.org
- [Bug 11714] New: Not a bug, but a suggestion â add an example like this: âPrice: â¬99 <small>(VAT included)</small>â bugzilla@jessica.w3.org
- [Bug 10828] i18n comment 4 : at least by default, <br> should constitute a bidi paragraph break bugzilla@jessica.w3.org
- [Bug 11712] typo: "labeld" should be "labeled" bugzilla@jessica.w3.org
- [Bug 11712] New: typo: "labeld" should be "labeled" bugzilla@jessica.w3.org
- [Bug 11234] Invalidate documents whose text content contains improperly balanced bidi formatting characters bugzilla@jessica.w3.org
- [Bug 11711] What about sandboxed XHTML ? bugzilla@jessica.w3.org
- [Bug 11234] Invalidate documents whose text content contains improperly balanced bidi formatting characters bugzilla@jessica.w3.org
- [Bug 11711] What about sandboxed XHTML ? bugzilla@jessica.w3.org
- [Bug 11711] New: What about sandboxed XHTML ? bugzilla@jessica.w3.org
Sunday, 9 January 2011
Saturday, 8 January 2011
- [Bug 11699] When calling input.focus(), should (a) the cursor be at the start, (b) the cursor be at the end or (c) the contents be selected? Please define bugzilla@jessica.w3.org
- [Bug 10808] text with unknown direction gets corrupted when inserted in content with opposite direction bugzilla@jessica.w3.org
- [Bug 10828] i18n comment 4 : at least by default, <br> should constitute a bidi paragraph break bugzilla@jessica.w3.org
- [Bug 11295] Make script-inserted external scripts that have .async=false execute in the insertion order, default to true bugzilla@jessica.w3.org
- [Bug 11699] When calling input.focus(), should (a) the cursor be at the start, (b) the cursor be at the end or (c) the contents be selected? Please define bugzilla@jessica.w3.org
- [Bug 11699] New: When calling input.focus(), should (a) the cursor be at the start, (b) the cursor be at the end or (c) the contents be selected? Please define bugzilla@jessica.w3.org
- [Bug 11670] "The setTransform(a, b, c, d, e, f) method must [...] invoke the transform(a, b, c, d, e, f) method" - so if I set CanvasRenderingContext2D.prototype.transform=function(){alert()}, then calling setTransform would trigger the alert? Probably this shouldn't bugzilla@jessica.w3.org
- [Bug 11695] import java.util.*; public class GeneralCalculation { static Scanner reader = new Scanner(System.in); public static void main(String[] args) { int Spearman, Slinger, Swordman, Planx, Archer, Sniper, Giro, Giant, Bomber, Ram, Catapult, Mortar, Doctor, Cook bugzilla@jessica.w3.org
- [Bug 11605] how to get forms values bugzilla@jessica.w3.org
- [Bug 11295] Make script-inserted external scripts that have .async=false execute in the insertion order, default to true bugzilla@jessica.w3.org
- [Bug 11295] Make script-inserted external scripts that have .async=false execute in the insertion order, default to true bugzilla@jessica.w3.org
Friday, 7 January 2011
- [Bug 11243] we should have a media element best practices section bugzilla@jessica.w3.org
- [Bug 11243] we should have a media element best practices section bugzilla@jessica.w3.org
- [Bug 11020] Update the style sheet for the W3C copy to set the font-size for <code> elements to 1em. bugzilla@jessica.w3.org
- [Bug 11205] The sentence describing when to fetch the poster resource is especially convoluted. bugzilla@jessica.w3.org
- [Bug 11205] The sentence describing when to fetch the poster resource is especially convoluted. bugzilla@jessica.w3.org
- [Bug 11293] please update WEBLINK ref bugzilla@jessica.w3.org
- [Bug 11293] please update WEBLINK ref bugzilla@jessica.w3.org
- [Bug 11295] Make script-inserted external scripts that have .async=false execute in the insertion order, default to true bugzilla@jessica.w3.org
- [Bug 11695] import java.util.*; public class GeneralCalculation { static Scanner reader = new Scanner(System.in); public static void main(String[] args) { int Spearman, Slinger, Swordman, Planx, Archer, Sniper, Giro, Giant, Bomber, Ram, Catapult, Mortar, Doctor, Cook bugzilla@jessica.w3.org
- [Bug 11695] New: import java.util.*; public class GeneralCalculation { static Scanner reader = new Scanner(System.in); public static void main(String[] args) { int Spearman, Slinger, Swordman, Planx, Archer, Sniper, Giro, Giant, Bomber, Ram, Catapult, Mortar, Doctor, Cook bugzilla@jessica.w3.org
- [Bug 11694] "best representation" does not define how to normalize decimal part of second bugzilla@jessica.w3.org
- [Bug 11694] New: "best representation" does not define how to normalize decimal part of second bugzilla@jessica.w3.org
- [Bug 11693] New: http://perjuanganulamadahulu.blogspot.com/ bugzilla@jessica.w3.org
- [Bug 11692] step 11: "a rel attribute whose value includes the bookmark keyword" is not well defined bugzilla@jessica.w3.org
- [Bug 11692] step 11: "a rel attribute whose value includes the bookmark keyword" is not well defined bugzilla@jessica.w3.org
- [Bug 11692] New: step 11: "a rel attribute whose value includes the bookmark keyword" is not well defined bugzilla@jessica.w3.org
- [Bug 11690] New: "need a date" not xreffed bugzilla@jessica.w3.org
- [Bug 11689] step 8: be explicit about the order in which things are located and removed bugzilla@jessica.w3.org
- [Bug 11689] New: step 8: be explicit about the order in which things are located and removed bugzilla@jessica.w3.org
- [Bug 11687] New: Make the non-normative parts of the definition of "application cache" into notes, to not mislead people into thinking they're normative. Only the list of what's in an appcache is normative here. bugzilla@jessica.w3.org
- [Bug 11688] New: Please add a note about loading appcache master entries that are listed in NETWORK section bugzilla@jessica.w3.org
Thursday, 6 January 2011
Wednesday, 5 January 2011
- [Bug 11674] really awesome! good job, dudes! bugzilla@jessica.w3.org
- [Bug 11674] really awesome! good job, dudes! bugzilla@jessica.w3.org
- [Bug 11347] Submitting a partially downloaded form bugzilla@jessica.w3.org
- [Bug 11137] Multiple-email inputs should require no space characters between values bugzilla@jessica.w3.org
- [Bug 11137] Multiple-email inputs should require no space characters between values bugzilla@jessica.w3.org
- [Bug 10838] Make <u> conforming. bugzilla@jessica.w3.org
- [Bug 11347] Submitting a partially downloaded form bugzilla@jessica.w3.org
- [Bug 11663] "non-shortest form" is more established than "overlong form" bugzilla@jessica.w3.org
- [Bug 11674] New: really awesome! good job, dudes! bugzilla@jessica.w3.org
- [Bug 11578] whitespace in pre bugzilla@jessica.w3.org
- [Bug 11673] I need to send live data from device to URL on remote system. Would be nice to connect WebSocket, but simple access to buffer callback to package and send data to remote URL. Having access to data after closing recording interupts asynchronous processin bugzilla@jessica.w3.org
- [Bug 11673] New: I need to send live data from device to URL on remote system. Would be nice to connect WebSocket, but simple access to buffer callback to package and send data to remote URL. Having access to data after closing recording interupts asynchronous processin bugzilla@jessica.w3.org
- [Bug 9452] Handling of additional tracks of a multitrack audio/video resource bugzilla@jessica.w3.org
- [Bug 11168] Remove WhatWG and html5.org references in status section of document bugzilla@jessica.w3.org
- [Bug 11124] consider reducing verbosity when talking about code points bugzilla@jessica.w3.org
- [Bug 10895] Use markup compatible with both HTML/XML syntax in examples bugzilla@jessica.w3.org
- [Bug 11671] New: Input Elements with state color and range and their attributes. bugzilla@jessica.w3.org
- [Bug 11602] define precisely how autoplay overrides preload bugzilla@jessica.w3.org
- [Bug 11670] New: "The setTransform(a, b, c, d, e, f) method must [...] invoke the transform(a, b, c, d, e, f) method" - so if I set CanvasRenderingContext2D.prototype.transform=function(){alert()}, then calling setTransform would trigger the alert? Probably this shouldn't bugzilla@jessica.w3.org
- [Bug 10694] Specify window.console bugzilla@jessica.w3.org
Tuesday, 4 January 2011
- [Bug 11229] Try making an author-specific edition that has one page per section, a tree on the side, and ben's styles, as per http://www.reddit.com/r/programming/comments/dzww6/who_edits_the_w3c_specs_they_look_like_a_ransom/c14ilc2 bugzilla@jessica.w3.org
- [Bug 11668] Make the following note into a security warning: "It is possible that the output of this algorithm, if parsed with an HTML parser, will not return the original tree structure." and add an example of an attack (ack Eduardo Vela Nava) bugzilla@jessica.w3.org
- [Bug 11668] New: Make the following note into a security warning: "It is possible that the output of this algorithm, if parsed with an HTML parser, will not return the original tree structure." and add an example of an attack (ack Eduardo Vela Nava) bugzilla@jessica.w3.org
- [Bug 11666] New: The value sanitisation algorithm should be clear that it sets the value property to the sanitized form. This is explicit in several cases but implicit in several cases. bugzilla@jessica.w3.org
- [Bug 11347] Submitting a partially downloaded form bugzilla@jessica.w3.org
- [Bug 11663] "non-shortest form" is more established than "overlong form" bugzilla@jessica.w3.org
- [Bug 11663] New: "non-shortest form" is more established than "overlong form" bugzilla@jessica.w3.org
- [Bug 11298] Surrogate catching doesn't belong in input stream preprocessing bugzilla@jessica.w3.org
- [Bug 11298] Surrogate catching doesn't belong in input stream preprocessing bugzilla@jessica.w3.org
- [Bug 11427] should allow use of xml:id for XHTML5 bugzilla@jessica.w3.org
- [Bug 11657] My worry is that this doesn't cover all the different kinds of textual transformations. Yes, it does cover obliqueness and weight, it does not cover letter spacing and other textual attributes that may be of some use to developers. bugzilla@jessica.w3.org
- [Bug 11657] New: My worry is that this doesn't cover all the different kinds of textual transformations. Yes, it does cover obliqueness and weight, it does not cover letter spacing and other textual attributes that may be of some use to developers. bugzilla@jessica.w3.org
- [Bug 10838] Make <u> conforming. bugzilla@jessica.w3.org
Monday, 3 January 2011
Sunday, 2 January 2011
Saturday, 1 January 2011
Last message date: Monday, 31 January 2011 22:47:21 UTC