Skip to content
This repository has been archived by the owner on Aug 7, 2019. It is now read-only.

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

Open
tbosch opened this issue Mar 12, 2013 · 3 comments
Open

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

tbosch opened this issue Mar 12, 2013 · 3 comments
Labels
bug

Comments

@tbosch
Copy link
Contributor

tbosch commented Mar 12, 2013

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
Copy link
Contributor Author

tbosch commented Mar 12, 2013

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
Copy link
Contributor Author

tbosch commented Mar 12, 2013

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
Copy link
Contributor Author

tbosch commented Apr 24, 2013

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tbosch