search

opitzconsulting / uitest.js

uitest.js is able to load a webpage into a frame, instrument that page and the javascript in that page (e.g. add additional scripts at the end of the document, ...) and execute actions on that page.
MIT License
67 stars 8 forks source link

Warning: FF19 Use of attributes' specified attribute is deprecated. It always returns true. #11

Open tbosch opened 11 years ago

tbosch commented 11 years ago

From an email of Marek:

Hello, errors are logged on standard FireFox Web Developer console (Shift+Ctrl+K) on Ubuntu.

FF 19 pointed line 331 by message: [08:24:17.883] Use of attributes' specified attribute is deprecated. It always returns true. @ http://test.vinci.org.pl:9000/test/dist/uitest.js:331

FF 11 shown: [08:20:17.920] Use of globalStorage is deprecated. Please use localStorage instead. @ http://test.vinci.org.pl:9000/test/test/ui/fixtures/basic.html?1362640817720 [08:20:19.326] Use of globalStorage is deprecated. Please use localStorage instead. @ http://test.vinci.org.pl:9000/test/test/ui/fixtures/basic.html?1362640819214#123 [08:20:19.628] Use of globalStorage is deprecated. Please use localStorage instead. @ ...

Best regards, Marek

tbosch commented 11 years ago

For the globalStore: We don't use it in any of our code. However, I could reproduce this problem on FF11 (WebConsole, not FireBug!).

tbosch commented 11 years ago

For the warning: "Use of globalStorage is deprecated. Please use localStorage instead": This is due to the fact that we are checking attr.defined. We are looping over the attributes of the <html> node to serialize it into a string. In older IEs, this would return all possible attributes (e.g. onchange, ...), because of which we are checking attr.defined. However, in current FF, this gives us a warning.

See this url for the jQuery team, as they had (and have) the same problem: http://bugs.jquery.com/ticket/12072

The problem is that when we try to feature test this, FF is already emitting the warning :-(

tbosch commented 11 years ago

With the new refactoring from #22 this issue will be solved.