Talk:Acid3
Add topicLatest comment: 1 month ago by Alfa-ketosav in topic Firefox
| This is the talk page for discussing improvements to the Acid3 article. This is not a forum for general discussion of the subject of the article. |
Article policies
|
| Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
Archives (index): 1, 2, 3, 4, 5Auto-archiving period: 3 months  |
 | This article is rated C-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||
| |||||||||||||||||||||
Firefox
[edit]Fx 152.0.1 scores 96/100 with the following failures (brackets are additions to the quote, only their contents are part of the syntax, but not the brackets themselves):
- Test 22: no exception for [document.]createElement('di<v'). That is, di<v is an invalid element name, but document.createElement parses di<v as if it be valid. I guess this is due to a change to document.createElement no more than 13 ya.
- Test 23: no exception for [document.]createElementNS('null', 'di<v'). Same as test 22, except for using document.createElementNS instead of document.createElement.
- Test 25: failed to raise exception. In the code, I found various messages that can be displayed depending on:
- whether an exception occurred upon trying to call document.createDocumentType with arguments of "a:" and 2 empty strings (i. e., having no illegal character but being malformed). If no exception happens, "failed to raise exception" is the message (bold here as being the message shown here).
- If an exception occurs:
- whether the code of the exception is equal to its NAMESPACE_ERR property: if not, the message is wrong exception.
- Otherwise: whether the exception has all constants (i. e., the INVALID_ACCESS_ERR property is 15). If it isn't, the message is "exceptions don't have all the constants".
- Test 35: expected '0' but got '1' - root element, with no parent node, claims to be a :first-child. This is an element-index-related message.