Closed Bug 1228797 Opened 9 years ago Closed 9 years ago

CSSUnprefixingService.js, line 271: TypeError: args[1].name is undefined

Categories

(Core :: CSS Parsing and Computation, defect)

defect
Not set
normal

Tracking

()

RESOLVED WONTFIX
Tracking Status
firefox45 --- affected

People

(Reporter: jruderman, Unassigned)

References

Details

(Keywords: testcase)

Attachments

(1 file)

Attached file q.html
With:
  user_pref("layout.css.unprefixing-service.globally-whitelisted", true);

JavaScript error: resource://gre/components/CSSUnprefixingService.js, line 271: TypeError: args[1].name is undefined
I think this works out correctly -- we'll reject the gradient expression (as we should, since it's invalid).

The JS-error-spam is annoying, but we'll be deprecating the CSSUnprefixingService soon (and won't be shipping it globally-enabled to any release versions ever, I think), once bug 1213126 lands.

So, to the extent that there's something to fix here, it's upstream css-fixme, where this webkit-gradient unprefixing script comes from. ( https://github.com/hallvors/css-fixme/ )
(In reply to Daniel Holbert [:dholbert] from comment #1)
> So, to the extent that there's something to fix here, it's upstream
> css-fixme, where this webkit-gradient unprefixing script comes from. (
> https://github.com/hallvors/css-fixme/ )

...though I can't trigger this error (in my error console) when pasting the testcase's webkit-gradient CSS into http://hallvord.com/temp/moz/cssfixme.php .  So maybe the upstream version doesn't get tripped up by this after all? Cool.

Anyway: given that this is just about some console-spew, in a JS-implemented service which is going away and which is only enabled by default on whitelisted sites anyway (for release builds), I'm going to say this is WONTFIX.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: