Closed Bug 1226114 Opened 9 years ago Closed 9 years ago

Bugzilla should have a better browser switch (creates various errors in the Browser Console)

Categories

(Bugzilla :: Bugzilla-General, defect)

Product:
Bugzilla
Component:
Bugzilla-General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED WONTFIX

People

(Reporter: BesTo, Unassigned)

Details

Bugzilla creates various errors in the Browser Console. I can make QA, if needed. Here a c&p of some: Error in parsing value for 'width'. Declaration dropped. show_bug.cgi Error in parsing value for 'font-weight'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:4:223 Expected 'none', URL, or filter function but found 'Alpha('. Error in parsing value for 'filter'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:8:548 Unknown property 'touch-action'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:8:844 Unknown property 'touch-action'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:8:985 Unknown property 'touch-action'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:8:1729 Unknown property 'touch-action'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:8:1865 Expected 'none', URL, or filter function but found 'alpha('. Error in parsing value for 'filter'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:8:11241 Unknown property 'touch-action'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:8:12269 Expected 'none', URL, or filter function but found 'Alpha('. Error in parsing value for 'filter'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:8:17575 Expected 'none', URL, or filter function but found 'Alpha('. Error in parsing value for 'filter'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:8:17725 Expected 'none', URL, or filter function but found 'Alpha('. Error in parsing value for 'filter'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:8:17800 Expected 'none', URL, or filter function but found 'Alpha('. Error in parsing value for 'filter'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:8:28416 Expected 'none', URL, or filter function but found 'Alpha('. Error in parsing value for 'filter'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:8:28599 Expected 'none', URL, or filter function but found 'Alpha('. Error in parsing value for 'filter'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:10:548 Unknown property 'touch-action'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:10:844 Unknown property 'touch-action'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:10:985 Unknown property 'touch-action'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:10:1729 Unknown property 'touch-action'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:10:1865 Expected 'none', URL, or filter function but found 'alpha('. Error in parsing value for 'filter'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:10:11241 Unknown property 'touch-action'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:10:12269 Expected 'none', URL, or filter function but found 'Alpha('. Error in parsing value for 'filter'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:12:2878 Expected 'none', URL, or filter function but found 'Alpha('. Error in parsing value for 'filter'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:12:3028 Expected 'none', URL, or filter function but found 'Alpha('. Error in parsing value for 'filter'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:12:3103 Expected 'none', URL, or filter function but found 'Alpha('. Error in parsing value for 'filter'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:12:13710 Expected 'none', URL, or filter function but found 'Alpha('. Error in parsing value for 'filter'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:12:13892 Unknown property '-moz-box-shadow'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:14:223 Unknown property 'user-select'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:14:571 Unknown property 'user-select'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:14:808 Error in parsing value for 'background-image'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:16:1888 Error in parsing value for 'background-image'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:16:2456 Error in parsing value for 'background-image'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:16:2827 Error in parsing value for 'background-image'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:16:3244 Error in parsing value for 'background-image'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:16:3642 Unknown property '-moz-box-shadow'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:16:4598 Error in parsing value for 'background'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:16:5002 Error in parsing value for 'background'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:16:6578 Error in parsing value for 'background-image'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:16:13401 Unknown property '-moz-box-shadow'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:16:14189 Unknown property '-moz-box-shadow'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:16:14783 Error in parsing value for 'background-image'. Declaration dropped. ffefb9618d3cb76266d944a8b9129098.css:16:15479 Error in parsing value for 'width'. Declaration dropped. page.cgi Error in parsing value for 'background-image'. Declaration dropped. datatable-base.css:8:746 Error in parsing value for 'background-image'. Declaration dropped. datatable-base.css:8:897 Error in parsing value for 'background-image'. Declaration dropped. datatable-base.css:8:968 Unknown property 'user-select'. Declaration dropped. datatable-sort.css:8:286 Expected declaration but found '*'. Skipped to next declaration. datatable-sort.css:8:469 Expected declaration but found '*'. Skipped to next declaration. gallery-datatable-row-expansion-bmo.css:1:201 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:16:14 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:17:14 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:18:14 Expected color but found 'top'. Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:19:30 Unknown property '-moz-border-radius'. Declaration dropped. persona-buttons.css:21:20 Unknown property '-moz-box-shadow'. Declaration dropped. persona-buttons.css:27:17 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:37:14 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:38:14 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:39:14 Expected color but found 'top'. Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:40:30 Unknown property '-moz-box-shadow'. Declaration dropped. persona-buttons.css:45:17 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:86:14 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:87:14 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:88:14 Expected color but found 'top'. Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:89:30 Unknown property '-moz-border-radius'. Declaration dropped. persona-buttons.css:91:20 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:113:14 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:114:14 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:115:14 Unknown property '-moz-box-shadow'. Declaration dropped. persona-buttons.css:118:17 Unknown property '-moz-border-radius'. Declaration dropped. persona-buttons.css:145:20 Unknown property '-moz-box-shadow'. Declaration dropped. persona-buttons.css:151:17 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:164:14 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:165:14 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:166:14 Expected color but found 'top'. Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:167:30 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:172:14 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:173:14 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:174:14 Expected color but found 'top'. Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:175:30 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:180:14 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:181:14 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:182:14 Expected color but found 'top'. Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:183:30 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:188:14 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:189:14 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:190:14 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:200:14 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:201:14 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:202:14 Expected color but found 'top'. Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:203:30 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:208:14 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:209:14 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:210:14 Expected color but found 'top'. Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:211:30 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:216:14 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:217:14 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:218:14 Expected color but found 'top'. Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:219:30 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:224:14 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:225:14 Error in parsing value for 'background'. Declaration dropped. persona-buttons.css:226:14
Part of this (persona-buttons.css, gallery-datatable-row-expansion-bmo.css) is not related to Bugzilla but bugzilla.mozilla.org code and hence out of scope for a Bugzilla task.
(In reply to Andre Klapper from comment #1) > Part of this (persona-buttons.css, gallery-datatable-row-expansion-bmo.css) > is not related to Bugzilla but bugzilla.mozilla.org code and hence out of > scope for a Bugzilla task. I expected that maybe the persona-buttons.css is a persona problem ... ... but I guess show_bug.cgi & page.cgi are bugzilla problems ... My intension was, that someone redirect the problems to the other projects, or - when the bugzilla errors are gone - I make new bug reports. But ATM there are just to much error msgs in the console to split this all by now ... ;-)
Assignee: general → nobody
Component: Bugzilla-General → User Interface
Product: Bugzilla → bugzilla.mozilla.org
QA Contact: default-qa
Version: unspecified → Production
these are CSS warnings, not errors, and can be safely ignored. in most cases they are required for compatibility with older browsers; especially the -moz prefixed properties. > But ATM there are just to much error msgs in the console to split this all by now if you're using firefox you can disable css warnings (click on the down arrow which is part of the "CSS" button and uncheck 'warnings').
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Please reopen the bug! The Browser Console should be used by Addon- & Website-Developers ... also to fix CSS-Errors ... If now Mozilla starts self with arguments like "Just turn it off.", why should anybody else use it, or try to make a clean Addon-/Page-Code ??? I think a browser- (version-) switch in Bugzilla should be not sooo difficult to implement.
Assignee: nobody → general
Status: RESOLVED → REOPENED
Component: User Interface → Bugzilla-General
Product: bugzilla.mozilla.org → Bugzilla
QA Contact: Tobias.Besemer
Resolution: INVALID → ---
Summary: Bugzilla creates various errors in the Browser Console → Bugzilla should have a better browser switch (creates various errors in the Browser Console)
Version: Production → unspecified
We don't want Bugzilla to sniff which browser you are using. Bugzilla follows web standards, which means that it doesn't use any -moz-foo value, for instance.
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: --- → WONTFIX
Uhh, is this about having an admin settable parameter to say which browsers that Bugzilla install should "support"? That doesn't sound like a correct approach, and I can't see any install would set this other than "all current major browsers". I mean, what happens when somebody with "incorrect" browser (yet alone browser version) comes along and that Bugzilla site breaks badly? Yeah, horrible things. Correct way is to do what we do currently and that's make sure all our supported browsers work correctly, without any additional params or settings. If that means to have some extra CSS hacks or settings then that's the price we have to pay. You can thank the browser makers for any of those! That said, please file individual bugs to address any warnings/errors in the syntax that you would like to fix in Bugzilla. Patches are also welcome, otherwise they might not get any traction due to limited developer resources. Fixes do need to make sure no major browser break, though. And please, search first for existing bugs, as I think we already have few improve HTML5/CSS type of bugs.
Status: RESOLVED → VERIFIED
(In reply to Teemu Mannermaa (:wicked) from comment #6) > Correct way is to do what we do currently and that's make sure all our > supported browsers work correctly, without any additional params or > settings. If that means to have some extra CSS hacks or settings then that's > the price we have to pay. You can thank the browser makers for any of those! (In reply to Tobias B. Besemer [:BesTo] (QA) from comment #4) > The Browser Console should be used by Addon- & Website-Developers ... also > to fix CSS-Errors ... > If now Mozilla starts self with arguments like "Just turn it off.", why > should anybody else use it, or try to make a clean Addon-/Page-Code ??? > > I think a browser- (version-) switch in Bugzilla should be not sooo > difficult to implement. Should I now really fill a bug for each error ??? Like: Error "Unknown property 'touch-action'. Declaration dropped." ??? I think this "bug" is question of QA/TechEvangelism ...
Flags: needinfo?(wicked)
Resolution: WONTFIX → FIXED
(In reply to Tobias B. Besemer [:BesTo] (QA) from comment #7) > Should I now really fill a bug for each error ??? You should group them to make more sense or if there's a common theme to the fixes. One bug per each error is a bit too much. > Like: Error "Unknown property 'touch-action'. Declaration dropped." ??? There's no such property used in Bugzilla. Note that BMO is heavily customized install and we (Bugzilla Project) can't influence it's contents at all. > I think this "bug" is question of QA/TechEvangelism ... What do you mean? I can't see anything our QA would do this. And only TechEvangelism I know is some Mozilla team (and I have no idea if they even do that anymore).
Flags: needinfo?(wicked)
Tech Evengelism lives at https://webcompat.com/ and all they do is contact the site maintainers with a potential way to fix the problem. In our case that would mean they'd file a bug here, which is already being done, so pointless here. :-) page.cgi is a hook file to call custom static page templates set up by the admin. Anything flagged on that is quite likely site-specific as well. show_bug.cgi could be Bugzilla itself, but I'd prefer seeing it reproduced on landfill.bugzilla.org first before reporting here. As mentioned elsewhere, bugzilla.mozilla.org is highly customized by Mozilla and we don't have influence over them. If you can't reproduce it on landfill then the bug belongs to them, and should be filed in the bugzilla.mozilla.org product instead of the Bugzilla product.
(In reply to Teemu Mannermaa (:wicked) from comment #8) > (In reply to Tobias B. Besemer [:BesTo] (QA) from comment #7) > > Should I now really fill a bug for each error ??? > > You should group them to make more sense or if there's a common theme to the > fixes. One bug per each error is a bit too much. > > > Like: Error "Unknown property 'touch-action'. Declaration dropped." ??? > > There's no such property used in Bugzilla. Note that BMO is heavily > customized install and we (Bugzilla Project) can't influence it's contents > at all. > > > I think this "bug" is question of QA/TechEvangelism ... > > What do you mean? I can't see anything our QA would do this. And only > TechEvangelism I know is some Mozilla team (and I have no idea if they even > do that anymore). OK, my intension at the beginning was to have e.g. this bug as a meta-/tracking-bug for this (kind of) problem(s) ... I think to solve this "problem(s)" is a question of the Quality of Bugzilla, or a question of the "Tech-Evangelism", Mozilla stands for ... Firefox have a Browser Console to show CCS-Erros/-Warnings, so that Addon-/Page-Developers can fix them ... for a good Quality of there product(s) and fulfill the request of "Tech-Evangelisms" in the web ... If now the Buzilla-Team of Mozilla starts with "Just ignore them!", or "Turn the feature in your Firefox Browser Console off!", why should any other Dev GAF what his product(s) do in the background ??? My intension wasn't to sav you Devs, what you should do! I can make a new bug with a FRQ for integrating https://modernizr.com/ into Bugzilla, so everybody that install Bugzilla can/should use it ... ... but my intension is "just" to remove the msgs - no matter how the Devs will do it!
Resolution: FIXED → WONTFIX
The only way to remove those warnings is to browser-sniff and send a custom CSS file for each browser, because each one needs a different set of attributes to work correctly. Since they all just ignore attributes they don't understand, there's no real issue with just sending them all (especially since browser-sniffing is generally evil), except that it puts those warnings on the console. Those warnings are good for catching real errors, but if the error mentions something that would be valid in a different browser then we just have to live with it.
(In reply to Dave Miller [:justdave] (justdave@bugzilla.org) from comment #11) > The only way to remove those warnings is to browser-sniff and send a custom > CSS file for each browser, because each one needs a different set of > attributes to work correctly. My idea was to load/have one file for all attributes that are standardized and understood by all browsers and load separate CSS-Files with only the attributes that can only understand some/one browser just for these/this browser. AFAIK do FF this also with the browser themes. After that should be in the browser console only errors visible that are really errors. Doing it e.g. with https://modernizr.com/ would have the benefit that the bugzilla team don't have to maintenance the code and there would be also some feedback/improvements to this project (e.g. via bug-reports). If using e.g. https://modernizr.com/ to manage the different browser at Mozilla-Sites would hopefully bring (after some time) a "quasi standard" to handle this and it would be much better/easier to work with the console, because sites that creates a lot of errors while browsing (e.g. GMail) should/have to follow this "quasi standard" to manage browsers better later, too.
You need to log in before you can comment on or make changes to this bug.