v151.0.4 session-memory change relating to radio button state?
My Home page is a local HTML file featuring a CSS-based tabbed notebook holding links organized into various categories. When exiting FF, I always have this page as the … (read more)
My Home page is a local HTML file featuring a CSS-based tabbed notebook holding links organized into various categories. When exiting FF, I always have this page as the active browser tab, so that on start-up it's still the active one in the event of multiple open browser tabs.
Until v151.0.4 (and still now with v152.0), if I exited FF with the active notebook tab (actually a styled radio button under the hood) in my CSS tabbed notebook something other than the first/leftmost tab, FF would restart with that being the active tab, but after a few seconds of CPU activity as the browser initialized the active notebook tab would switch to the first/leftmost one. (In my HTML I also have <input type="radio" name="tabs" checked> specified for this first/leftmost instance.)
Since the update, however, it remains stuck on the one from the last browser session as first displayed. I suppose I can live with this, but I do wonder what accounts for the change in behavior. If it's by design, where is it documented? If not ... maybe it calls for a bug report.