same thing with meHuh, I just installed this add-on to try it out, and all but one of the add-on buttons in my navigation toolbar disappeared

Moderators: satrow, FranklinDM, Lootyhoof
same thing with meHuh, I just installed this add-on to try it out, and all but one of the add-on buttons in my navigation toolbar disappeared
Hehehe...gracious1 wrote:...custom toolbar Foo Bar. ...
So your toolbar looks like this…[DarKwiN] wrote:I found another problem related to toolbar: when installing Reader View, the refresh/stop button I've got on the right end of URL box gets thrown out of the URL box and divided in two split buttons (the refresh one and the stop one).
Disabling Reader View fixes the problem. Attached to the post you'll find a screenshot describing the situation.
Thanx!!
I think I said that in the post above....[DarKwiN] wrote:Nice tip, thank you!
I further examined the issue, and I could pin down the problem to simply not putting Reader View (or any other) button between Reload and Stop.
Anything but the stop button (if you want them to be unified)![DarKwiN] wrote:Anything between them not only cause them to split, but also prevent the Reload button to be nicely put in the URL box. No problem putting anything to the left of the Reload button.
You're welcome.Thanx again!
yes, the extension does not work for pages loaded in background, and because of this I made a separate button:have to frequently reload pages for a page to become readable by the add-on.]
Code: Select all
ReaderParent.toggleReaderMode(event);
Where exactly do you put the code?jars_ wrote: yes, the extension does not work for pages loaded in background, and because of this I made a separate button:Code: Select all
ReaderParent.toggleReaderMode(event);
Wow, thank you for the quick reply and quick fix!Isengrim wrote:I am currently working on a fix for this. It has to do with some of the code I borrowed from the original browser's codebase working differently in the context of an extension. I have a tentative fix in place in my development environment, but I want to do some more testing to make sure it's ready.
For now, selecting a background-loaded tab and refreshing it should cause the button to update correctly. Force-toggling Reader Mode also works I guess, but it should not be necessary after the next update.
Edit: The issue is also on the Github repo, #15.
Well, I just realized that all of the localizations are incomplete, which will cause some breakage... so I'm roughing in some missing translations first.f-117 wrote:So, what will you be working on next in the "Issues" list?