FF57 looking up for me

[RobertJ]

.
Have been using FF Nightly (57alpha) for all my browsing (almost) for two weeks now. Am now starting to believe it will work for me. Reasoning is:

userChrome.css will likely remain, hopefully

on August 11, 2017 at 7:59 am:
There are no plans to drop userChrome.css that I’m aware of.

If true I assume that is because userChrome.css does static tweaks as opposed to extension driven tweaks (just a guess).

I have found that two add-ons critical to me are either ported (uBlock Origin) or have a great replacement (Cookie AutoDelete). In the latter case the add-on has provisions for a white list and removes cookies associated with a tab a short time after closing the tab. Also has some other good features.

There is also this site which is tracking the status of many add-ons.

Of interest to me are:

• Flagfox
  Greasemonkey
  NoScript
  RefControl
  Video DownloadHelper

They will likely be ported or a replacement is indicated.

I noted that FF57 seems to work for almost all my browsing. I have found that Palemoon with a couple of legacy add-ons completes the picture. In this latter case I use it to pass through paywalls on some news sites. Perhaps FF57 with the evolving add-ons will fill the bill.

.

[Brummelchen]

Cookie Autodelete is a chrome cobversion, Vanilla COokieManager is the more known.

GM -> WE, or get ViolentMonkey (faster), Tampermonkey is not my favorite
NS -> WE
RC -> dunno, not needed
VDH -> dead

it takes time

bwt forget that stupid google-doc - go
https://addons.mozilla.org/en-us/firefo ... ppver=57.0

[flaneurb]

It's stupid because you don't like it or ???

[RobertJ]

.
According to VDH site they are porting, we will see.

bwt forget that stupid google-doc - go
https://addons.mozilla.org/en-us/firefo ... ppver=57.0

Those on that URL are already ported, I'm looking at the future and what may happen.

Also, some type of referrer add-on is needed in combination with cookie manipulation to bypass certain paywalls.

.

[Brummelchen]

i think i had a posting here, gone?

i cant remember all, so i write short.

the google doc is nice to have a foreview, but tahts all, its neither current nor final.

refcontrol is not present but its already there:
from https://chrome.google.com/webstore/deta ... doihckciin
to https://addons.mozilla.org/en-us/firefo ... ercontrol/
same author, same code.

same for "cookie autodelete" which is similar to "navilla cookie manager" which was first and still working (my choice in chromium)
i still need to debug bbcode and text insert for storage but at least they work. none of those are currently available for firefox.
at least mozilla has benefit from chrome store, many extension were converted, some were developed from scratch.
download a chrome extension, edit the manifest and try it in v57, you can also debug those. some api is not ready (eg tabs and sessions), but the most will work. thats why there exist no session manager for firefox, only grouping extensions like "tab saver" or when ready OneTab.

HTH

[Tomatoshadow2]

I really agree, Firefox 57, is looking like it is going in an awesome direction!

[JodyThornton]

I actually like the Photon interface. userChrome editing allows me to place the tab bar underneath the address bar. And the performance is terrific. So now I have a classic-styed browser in terms of placement, but modern in terms of look.

[RobertJ]

.
JodyThornton, did you already know the id/class of the relevant objects or did you find them without the DOMi? If the latter how?

.

[JodyThornton]

Hi RobertJ:

I simply placed this in the userChrome.css file, to allow me to change the address bar:

@namespace url("http://www.mozilla.org/keymaster/gateke ... s.only.xul"); /* only needed once */

#TabsToolbar{-moz-box-ordinal-group:10000!important}


As for Photon, it's enabled, but when I ran Nightly 56, I changed a setting in about:config to "true" It appears missing now

[RobertJ]

.
Thanks. Unless you know the id/class, without the DOMi you likely will have to search through the app css and try to find it. A very tedious and maybe fruitless task.

.

[JodyThornton]

I would not have know ANY of that RobertJ

[Aris]

.
Thanks. Unless you know the id/class, without the DOMi you likely will have to search through the app css and try to find it. A very tedious and maybe fruitless task.

.

Fx 57+ offers a way to find ids/classes for items by clicking on them.
It is not as nice as in Dom Inspector + Element Inspector, but still better than looking through browsers.css files especially since we can not extract omni.ja anymore, because they changed file compression methods to save a few KBs and no software is able to unpack/decompress those files properly atm. But that is a different story.

Nightly > Tools > Web Developer > Toggle Tools > Toolbox Options (wheel icon on developer toolbar) >
Advanced settings > Check 'Enable browser chrome and add-on debugging toolboxes' and 'Enable remote debugging'

Restart Nightly

Nightly > Tools > Web Developer > Browser Toolbox (or Ctrl+Alt+Shift+I)

The newly opened window shows the dom code of the main window. In the top left corner you see a button called "Pick an element from the page". Now you are able to use your mouse cursor on any ui item on main window and the other window will jump to items (xul) code.

https://i.imgur.com/tJHPTrO.png

[RobertJ]

.
Aris, thank you. Takes a bit of getting used to but definitely a BIG improvement to sorting through app css, assuming you can unpack the jar files.

.

[Brummelchen]

RobertJ, i already mentioned it, remember?
http://forums.mozillazine.org/viewtopic ... #p14764973

[RobertJ]

RobertJ, i already mentioned it, remember?
http://forums.mozillazine.org/viewtopic ... #p14764973

You did but in viewing that post I still find it rather incomprehensible unlike the one from Aris which is quite clear.

.