You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Actual result: when the Firefox window reopens with the local HTML file as the active tab, the window is not renamed by Crappy Firetitle. The workaround is to refresh the tab, then the renaming is working.
Expected result: to have the window renamed right after Firefox restarted without manual refresh.
More info: About my workflow: I have several Firefox windows, each containing tens of tabs, including several local HTML files. Say I have 10 windows, so 10 "active" tabs (one per window). Say there are 6 active tabs that are local HTML files. It means that if I close Firefox, the next time I open it, there will be only 4 windows that are successfully renamed, and I'll have to manually refresh the other 6 local active tabs to have all my Firefox windows renamed.
My config: Crappy Firetitle 0.1.12 on Firefox 69.0 and Xubuntu 19.04.
The text was updated successfully, but these errors were encountered:
Steps to reproduce the bug:
n
.file:///home/...
).Actual result: when the Firefox window reopens with the local HTML file as the active tab, the window is not renamed by Crappy Firetitle. The workaround is to refresh the tab, then the renaming is working.
Expected result: to have the window renamed right after Firefox restarted without manual refresh.
More info: About my workflow: I have several Firefox windows, each containing tens of tabs, including several local HTML files. Say I have 10 windows, so 10 "active" tabs (one per window). Say there are 6 active tabs that are local HTML files. It means that if I close Firefox, the next time I open it, there will be only 4 windows that are successfully renamed, and I'll have to manually refresh the other 6 local active tabs to have all my Firefox windows renamed.
My config: Crappy Firetitle 0.1.12 on Firefox 69.0 and Xubuntu 19.04.
The text was updated successfully, but these errors were encountered: