476719 - Web page bookmark opening a sidebar should give the sidebar focus

Status: RESOLVED INACTIVE

(Firefox :: Bookmarks & History, enhancement)

Description

[Honza Bambas (:mayhemer)]

Because window.focus() is unspecified and found annoying, the application (the browser) should be responsible for making the sidebar content focused when user open it by clicking a bookmark set to open in a sidebar. The same is made for any browser (Firefox) sidebar, such as history or bookmarks.

If this is not possible, it would be great to have some workaround for web application to make the sidebar focused them self.

Comment 1

[Tyler Downer [He/Him]]

Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles

Comment 2

[Marco Bonardo [:mak] (Away 10-21 August)]

looks like an enh request for sidebar, not sure if sidebar will be retained as a core feature, but no reason to close this.

Comment 3

[BMO Automation]

Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.

Comment 4

[Maciej Jaros]

I've confirmed this bug still occurs with FF 63. Example steps:

1. Install extension for opening bookmarks in sidebar (e.g. [1])
2. Add bookmark to Google translate.
3. Open bookmark normally in tab (notice how you have focus in left textarea).
4. Open bookmark in sidebar.

Result:
Focus remains in the main area of the tab.

Expected result:
Focus should be given to the sidebar.

[1] = https://addons.mozilla.org/en-US/firefox/addon/open-link-in-sidebar/

Comment 5

[Mark Banner (:standard8)]

Hi Maciej, please could you file a separate bug under the WebExtensions product. Although the bookmark handling is similar to the sidebar for web extensions, it is different code, and would be better handled in a fresh bug, rather than reopening this one.