608502 - A couple of declarations dropped (background-image-opacity in tabview.css and size, position, width, and height in tabview.html)

Status: RESOLVED FIXED

(Firefox Graveyard :: Panorama, defect, P4)

Description

[Robert Strong (they/them - no direct email)]

Seen in a Mac OS X debug build though I suspect this applies at least to some extent to all platforms.

TEST-START | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_apptabs.js
TEST-INFO | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_apptabs.js | Console message: [JavaScript Warning: "Unknown property 'background-image-opacity'.  Declaration dropped." {file: "chrome://browser/skin/tabview/tabview.css" line: 335}]
TEST-INFO | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_apptabs.js | Console message: [JavaScript Warning: "Error in parsing value for 'size'.  Declaration dropped." {file: "chrome://browser/content/tabview.html" line: 0}]
TEST-INFO | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_apptabs.js | Console message: [JavaScript Warning: "Error in parsing value for 'position'.  Declaration dropped." {file: "chrome://browser/content/tabview.html" line: 0}]
TEST-INFO | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_apptabs.js | Console message: [JavaScript Warning: "Error in parsing value for 'width'.  Declaration dropped." {file: "chrome://browser/content/tabview.html" line: 0}]
TEST-INFO | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_apptabs.js | Console message: [JavaScript Warning: "Error in parsing value for 'height'.  Declaration dropped." {file: "chrome://browser/content/tabview.html" line: 0}]

Comment 1

[Ian Gilman [:iangilman]]

Tim, you've fixed a number of these in other patches, yes? Can this be closed?

Comment 2

[Tim Taubert [:ttaubert] (inactive)]

They all should be fixed by bug 622288.

Comment 3

[Ian Gilman [:iangilman]]

bug 622288 has landed, so these should be fixed now