-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal: expose the new tab URL #470
Comments
(BTW: Blank URL is Interesting question. New Tab URL is indeed inconsistent, which is a browser specific URL. And it is a fake URL, for example, It would be helpful if there was a consistent way to judge these URLs. |
Some additional common URLs.
Different browsers may have significant differences. But extensions sometimes need to guide users to adjust certain settings, such as setting shortcuts, run in incognito mode, site permissions, allow access file URL, etc. In these cases, developers can only write user guide separately. |
A common usecase for extensions is when opening new tabs. If the user is already on the new tab page, it does not always make sense to open another tab, but to just replace the new tab page. |
I added Safari's values to @hanguokai's table above. |
In Opera it's |
Considering there are so many alternatives, and potentially also extension URLs used as new tab page. Would it not make sense to introduce a boolean typed |
Before proposing a solution, we first need to collect and determine what users(developers) needs are. For example,
Welcome to add your needs. |
(I don't know if the browser is willing to support it, I'm putting this issue here) Another common hardcoded URL is the product page (especially the writing review link) of the extension store. Developers have recently discussed this issue. The link needs to be modified to a specific store link before each release. A simple solution is adding a Considering all the common URLs listed above, and the different implementations of different browsers, we should design a flexible API. |
@hanguokai while I see value in further exploring handling any kind of special page and / or URL and how extensions interact with them across browsers, the original issue was about figuring out if a certain tab is a new tab page or not. This use case for tab archive extensions and for the use case I described, being able as developer to figure out if the current tab is a new tab page so it can overwrite it, if not, open a new tab. For both use cases, the proposed solution, exposing A few benefits:
|
@carlosjeurissen Don't worry, we are all just expressing our ideas, and we don't have the final say. |
@carlosjeurissen Do you suggest open a new issue for a general solution? |
@hanguokai yeah, I think this makes sense. The current issue is more about detecting if you are on a new tab page, while some of the use cases you are describing are more about being able to open special pages. The ability to open the management page and keyboard shortcuts page of the extension would be very useful. Opening the reviews page might be a bit more tricky as there is no 1:1 connection with stores and browsers. In addition, an extension could be installed without being on a store. |
I will open a new issue. For |
I took the liberty of adding the user's current and the browser's default homepage to the table in @hanguokai's comment. |
More ideas:
The benefit is that there'll be no need to request the |
Can you potentially add this to #473 as well? |
You overlooked something? He already updated the table in two issues at the same time two days ago. |
Assumed it was only updated here. Thanks for noting! |
Added
opposed: firefox
|
Even among Chromium browsers, the URL of a blank tab isn't consistent:
Chrome, Brave: chrome://newtab/
Edge: edge://newtab/
I propose to add:
I'm also fine naming it "NEW_TAB_URL".
My extension auto-archives old tabs. There's no point in archiving blank tabs, so I need to separate them from the rest. Currently, I need to hardcode blank tab URLs for each browser.
The text was updated successfully, but these errors were encountered: