Sidebar stealing focus

[A Former User]

A Former User last edited by

If tab is created with eg:
chrome.tabs.create({'url': 'https://www.google.com', 'active': true});

from any extension that uses browserAction, search form will be focused (after popup is gone and focus is on that tab)
but if tab is created/updated from sidebar extension with this method, form never gets focused except if user literally clicks on form

can this be fixed? ...I hope it's not intended behavior
opening Google, DuckDuckGo... etc. from sidebar, breaks functionality in some way

[shwetankdixit]

shwetankdixit last edited by

The sidebar extension is supposed to be more persistent. Even if clicking soemwhere on the sidebar produces a new tab, it is quite reasonable to expect that the user still wants to focus on the sidebar. I'm open to changing my opinion though, so please do let me know of any example extensions or use cases where it might be very cumbersome.

[A Former User]

A Former User last edited by

@shwetankdixit
well, one of the users of my V7 Bookamrks extension pointed out the problem (in thread about "zoom scope"), but it applies to pretty much any extensions that opens url's or switch tabs (bookmarks, notes, tabs extensions etc)

He (student975) stated that when opening search engines like DuckDuckGo, he expect search field to be focused and ready for keyboard input... which is proper behavior for that type of sites

[student975]

student975 last edited by

The sidebar extension is supposed to be more persistent. Even if clicking soemwhere on the sidebar produces a new tab, it is quite reasonable to expect that the user still wants to focus on the sidebar.

Sorry, I don't grok thees statements in a common, that is I don't see those reasons for "supposed to be more persistent" and "the user still wants to focus on the sidebar" to be the only use cases. Yes, there are use cases supporting these statements, and there are use cases with opposite sense - bookmarks panel is one of them.

I would more understand "it is up to sidebar to decide which focus policy is handy for user".

[A Former User]

A Former User last edited by

@shwetankdixit
I have another issue about sidebar focus (actually, just the opposite)
I'm trying to implement ctrl+left/right arrow keyboard shortcuts in one of my extension

but that kb. shortcut is also for navigating tab history
strange thing is, my focus is completely on sidebar, not on tab
and still, when performing that shortcut, it does the job in my extension (in SB)
and also it navigates trough tab history as parallel job.

So I'm thinking to implement shift instead of ctrl
but still, I have a feeling that I will eventually stumble upon this problem again
is that how it should be? ... (keyboard actions shared between tab and sidebar)
....or is it a bug?

UPDATE:
I definitely think it's a bug
it doesn't happen if I only open sidebar extension
but if I open extension, switch focus on tab and then back to sidebar
...then shortcut is fired on previously focused tab too

[shwetankdixit]

shwetankdixit last edited by

Thanks ... would it be possible for you to file a bug? If so, then let me know the bug number

[A Former User]

A Former User last edited by

here it is
DNA-50059

[A Former User]

A Former User last edited by

@shwetankdixit
btw. I prevented default, and made my own custom kb shortcuts
works fine without conflicting tab actions