Graham Perrin

Thanks. Now, your comment makes sense. I was previously confused because https://github.com/Noitidart/Chrome-Store-Foxified/issues/135#partial-discussion-header "workaround method" meant nothing to me, and https://github.com/Noitidart/Chrome-Store-Foxified/issues/135#issue-508060658 neither a workaround nor a method was described.

> `.pdf` @HubJ Chrome Store Foxified is intended for use with extensions, not PDF documents.

Ah, a workaround: ☑ Always open Cookie Quick Manager in new tab ---- I wondered whether my `userChrome.css` (for Vertical Tabs Reloaded) is a problem: ```text grahamperrin@momh167-gjp4-8570p:~/.mozilla/firefox/58ectoj2.default/chrome % cat userChrome.css...

Correct me, please, if I'm wrong: * whilst some types of legacy extension may be modified for use with Waterfox Current, Waterfox Current is not intended for use with **non**-modified...

As a side note, e10s is enabled by default in Waterfox 56 and not automatically disabled when incompatible extensions are enabled.

> … patches to run CAA in non-e10 window are welcome. I'd love to contribute but (sorry) no relevant coding skills. @MrAlex94 please: for the next release of Waterfox (56.2.4,...

(Convoluted workaround for Waterfox non-e10s windows moved to .)

Thanks! 1.2.1b1 is much better. Hopefully no longer any situation in which the modal dialogue will appear. ### A couple of edge cases #### 1 A special URL e.g. `about:`…...

1.2.1b2 feels regressive compared to 1.2.1b1. I could not remember the two-step workaround that I edited out of the foot of (opening post) . After I called up an archived...

I seem to get mixed results with 1.2.1b3. The first impression was good; it was easy to get a window with caa: working. Later use of the same profile was...