374112 - This use of E4X setName causes "Assertion failure: !IS_EMPTY(nameqn->uri)"This use of E4X setName causes "Assertion failure: !IS_EMPTY(nameqn->uri)" This use of E4X setName causes "Assertion failure: !IS_EMPTY(nameqn->uri)"
325750 - e4x/Expressions/11.1.4-08.js: inconsistencies in the use of {} syntax Part Deux
Assuming I have the tests setup correctly, ... 50: FAIL expected: valid, actual: invalid input: u='http://a.uri/'; p='p'; a=<a xmlns:p={u}> <{p}:b>x</p:b> </a>; output: SyntaxError: illegal XML character 51: FAIL expected: valid, actual: invalid input: u='http://a.uri/'; p='p'; a=<a xmlns:pp={u}> <p{p}:b>x</pp:b> </a>; output: SyntaxError: illegal XML character 53: FAIL expected: valid, actual: in
111207 - Implement clientLeft and clientTop
When I run the following page <html> <head> <title>scrollable div</title> <script type="text/javascript"> function inspectNewProperties (node) { var props = ['clientLeft', 'clientTop', 'clientWidth', 'clientHeight', 'scrollLeft', 'scrollTop', 'scrollWidth', 'scrollHeight']; output('Inspection of ' + node + ':'); for (var i = 0; i < props.length; i++) output(props[i] + ': ' + node[props[i]]); outpu
366483 - XMLToXMLString namespace redeclaration omissions
Our implementation (and I believe the E4X spec, tho I haven't taken the time to investigate fully) don't properly emit redeclarations for prefixes which are overridden with a different namespace in nested child elements. Two examples: // Example 1 XML.prettyPrinting = false; default xml namespace = "a"; var x = <m/>; default xml namespace = ""; var c = <y/>; x.appendChild(c); print(x.toXMLString()
369394 - Invalid whitespace chomping of XML literals
print(<a> b<c/></a> == <a>b<c/></a>); // == XML.ignoreWhitespace, not false This is probably (not tested yet) due to: http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/js/src/jsxml.c&rev=3.140&mark=1572#1567 A similar effect might happen at: http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/js/src/jsxml.c&rev=3.140&mark=3357#3350 except that the only way it can happen is for DeepCopy to be cal
366117 - Update XMLToXMLString for ECMA-354 ed. 2
The numbering of the steps for converting an element to a string in jsxml.c are based on ECMA-354 edition 1, which isn't the version made available on the ECMA site. (I don't even know where one would find ed. 1 now -- I feel lucky to have a copy of it.) This makes comparing code to spec difficult, so we should update the code to reflect the 2nd ed. numbering. I don't of any bugs the 2nd ed. wordi
258223 - Bookmark keyword quicksearch need a way to specify character encoding for query URLs
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616 using the quicksearch feature in Mozilla and Firefox to search for non ASCII search items often result in the said search item to be sent to website in non-universal encoding. I cannot decipher what encoding it is being sent, bu
309438 - Accept: header too long on account of text types
See bug 240493. The text types are text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8 These were added long ago, in a couple of steps. One big jump came in bug 83458, but bug 58040 started the bloat from */*. The comments are funny to read after all these years -- WAP/WML? It is to laugh. [Ok, amazon.com did serve content, and may still for all I know, in some such for
338621 - Feed View overrides XSLT stylesheet defined in XML document
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1a2) Gecko/20060517 BonEcho/2.0a2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1a2) Gecko/20060517 BonEcho/2.0a2 I am currently remaking my web site using XML and XSLT (don't worry, I will make HTML versions for accessibility and search indexing). I decided to offer RSS and Atom feeds to my web site and
333678 - E4X: extra " / > \n in Function.toSource
E4X: extra " / > \n in Function.toSource function a(){ a=<?xml version="1.0"?> a1=<{a} a="a"/>; a2=<{a} a="a"></a>; a3=<{a} a="a">1</a>; x=<a> a new line then a backslash \ then a slash <b a="aa \ "/></a> } a give ==> function a() { a = <?xml "version=\"1.0\""?>; a1 = <{a} a="a"/>/>; a2 = <{a} a="a">></a>; a3 = <{a} a="a">>1</a>; x = <a> a new line \n then a backslash \\ then a slash <b a="aa \n \
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
357471 - No xmlns for namespace with explicit prefix attached to an element via an attribute
336355 - E4X: .. accessor and wildcard with a node or attribute in filter
235441 - Capture event listeners fire on target (?!)
18333 - (incrementalxml) XML Content Sink should be incremental
253125 - cleanup gratuitous use of NS_ERROR_FACTORY_REGISTER_AGAIN
366417 - Adding <html:script src="data:..."> to XUL document no longer executes the script
http://bugzilla.mozilla.gr.jp/show_bug.cgi?id=5413
307895 - Date.toLocalFormat("%x") with format yyyy/MM/dd produces yyyy/MM/yyyy
358257 - Add support for XTF attributes
355827 - SpiderMonkey's readline() can't distinguish EOF