Status

()

Firefox
Extension Compatibility
RESOLVED INVALID
3 years ago
3 years ago

People

(Reporter: David Pelletier, Unassigned)

Tracking

41 Branch
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

3 years ago
Created attachment 8672398 [details]
firefox_theme_override.png

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:41.0) Gecko/20100101 Firefox/41.0
Build ID: 20151001175629

Steps to reproduce:

Install the BigTheme Extensions and use any Theme (i use the darkfox theme).



Actual results:

The CSS of the theme affect the about:memory tabs by overriding the text color. We can't see the text because it's the same color of the background. See the file attachement. If i desactived the module bigTheme, the css rules will not be overridden anymore.


Expected results:

The CSS shouldn't be override by the extension. The Color isn't set in the css of the about:memory page, so any global css color rule can change the color of the text.

Comment 1

3 years ago
Why are you reporting this here instead of the extension author's bug tracker?
https://github.com/wesj/bigTheme/issues

The extension is already marked as preliminarily reviewed, so I don't see what else could be done here.

“What does it mean if an add-on is 'experimental' or 'preliminarily reviewed'?
 Experimental add-ons have been checked by our editors to make sure they don't have security problems, but they may still have bugs or not work properly. Use caution when installing experimental add-ons and uninstall the add-on immediately if you notice problems.”
— https://addons.mozilla.org/faq

―――――

Wesley, are you the author of this extension? If so, please comment. Otherwise, my apologies; it's a case of mistaken identity.
Component: Untriaged → Extension Compatibility
Flags: needinfo?(wjohnston2000)
(Reporter)

Comment 2

3 years ago
(In reply to Gingerbread Man from comment #1)
> Why are you reporting this here instead of the extension author's bug
> tracker?
> https://github.com/wesj/bigTheme/issues
> 
> The extension is already marked as preliminarily reviewed, so I don't see
> what else could be done here.
> 
> “What does it mean if an add-on is 'experimental' or 'preliminarily
> reviewed'?
>  Experimental add-ons have been checked by our editors to make sure they
> don't have security problems, but they may still have bugs or not work
> properly. Use caution when installing experimental add-ons and uninstall the
> add-on immediately if you notice problems.”
> — https://addons.mozilla.org/faq
> 
> ―――――
> 
> Wesley, are you the author of this extension? If so, please comment.
> Otherwise, my apologies; it's a case of mistaken identity.

First, i was looking for a link or a button, to report the bug directly to the creator of the extension, on the add-on details webpage, but didn't find one. Why not have an option to send a bug report to the author directly (like a small forms), because otherwise many people use the review form to tell to the editor that the extension don't work. For me a review is not to exchange information to correct a bug, but to talk about the quality of the add-on.

The reason i post the bug here, it's because if the css rule was well specified in the about:memory page, the theme would not override the text-color property. I will report the bug on the github projet page.
Ouch! Thanks for the report. I'll see what I can do. Let's close this as invalid and I'll open something on github.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 3 years ago
Flags: needinfo?(wjohnston2000)
Resolution: --- → INVALID

Comment 4

3 years ago
(In reply to David Pelletier from comment #2)
> First, i was looking for a link or a button, to report the bug directly to
> the creator of the extension, on the add-on details webpage, but didn't find
> one.

Look to the right side of the “About this Add-on” box: in this case, there's a link labeled “Support site”. In other cases, it may be called “Support e-mail” or “Add-on home page”.
You need to log in before you can comment on or make changes to this bug.