Yes... your on the latest from what
Well hot heck!! Newbie does not embarrass himself!!
Yes... your on the latest from what
Code: Select all
#context-setDesktopBackground, #context-sendimage {
display: none !important;
}
I think that code is safe. Complicated CSS might cause some noticeable performance issues. I'm thinking fancy shadows and transforms and things of that nature. But hiding a couple of menu entries is pretty safe.GHM113 wrote:I finally figured out how to hide context menu items and added this code to userchrome.css:The question is: can this particular code or any .css code cause performance degradation? I am a bit paranoid after I discovered NoScript 5 uses synchronous API for content blocking.Code: Select all
#context-setDesktopBackground, #context-sendimage { display: none !important; }
I haven't seen any bugs about killing userChrome yet and the Fx 57 branch point is on the 2nd of August so that would probably be cutting things a bit close. They may have changed the version on which they want to end support (or perhaps they have reconsidered completely). If you do see a bug pop up for this please do let us know.smsmith wrote:I think that code is safe. Complicated CSS might cause some noticeable performance issues. I'm thinking fancy shadows and transforms and things of that nature. But hiding a couple of menu entries is pretty safe.GHM113 wrote:I finally figured out how to hide context menu items and added this code to userchrome.css:The question is: can this particular code or any .css code cause performance degradation? I am a bit paranoid after I discovered NoScript 5 uses synchronous API for content blocking.Code: Select all
#context-setDesktopBackground, #context-sendimage { display: none !important; }
However, talk of the town is userChrome is going away. Supposed to be Fx 57 that it stopped being supported, as I recall. Maybe now that the 57 train is coming into the station they will evaluate whether or not they can really kill it in time.
Thank you!smsmith wrote:I think that code is safe. Complicated CSS might cause some noticeable performance issues. I'm thinking fancy shadows and transforms and things of that nature.
As far as I remember, someone from Firefox team wrote in Firefox blog there were no plans to remove userchrome.sciguyryan wrote:I haven't seen any bugs about killing userChrome yet and the Fx 57 branch point is on the 2nd of August so that would probably be cutting things a bit close. They may have changed the version on which they want to end support (or perhaps they have reconsidered completely). If you do see a bug pop up for this please do let us know.