guilryder / chrome-extensions Goto Github PK

Is it possible that you can upload your plugin into the Microsoft App Store ?

This started to happen quite recently. I can only see it on Edge (version 90.0.818.51) and on Edge Beta (version 91.0.864.11).

1. Set format to {title} - [{protocol}://{hostname}{port}/] TEST
2. Visit any site e.g. https://www.etoro.com/login
3. Check page title:
   Expected: eToro - [https:///www.etoro.com/] TEST
   Actual: eToro - [https:///www.etoro.com/] TEST - [https:///www.etoro.com/] TEST ...
   
   Looks like the suffix is appened indefinitely.

Add the ability to extract a specific argument from the URL into the title.

Example URL: https://example.com/?login=saml&email=test%40example.com with the title “Sign-In”

Example:

The tag could be {argvalue=”key”} with “key” being the argument key to search for to return the value. Need to consider arguements prefaced by both “?” and “&”.

Tab title format: {title} - {protocol}://{hostnameascii} - {argvalue=email}

Result: Sign In - https://example.com/ - test%40example.com

Looks like cookies from sites loaded in iframes may be being handled differently from sites loaded directly. The below page loads fine when loaded directly with 3rd party cookies disabled, but failes when loaded in an iframe with your extension in place. Loads fine with cookies opened up.

Site tested: https://www.wunderground.com/

This may be out of scope for your simple extension but it would be nice if you or someone else could find a fix.

Hi!
First of all, thanks for the Url in Title extension. It's very useful when used together with KeePass.
Recently I noticed that it stopped working for some websites in Edge. Would it be possible to fix the issue?
For example etoro.com
It works correctly in Chrome.

Edge 90.0.818.8 Beta

Would it be possible to show subdomains, i.e. extract them from the hostname or just extract arbitrary regex from the variables?

The tab title format could look like {subdomain[x]} which could then be parsed and used with document.location.hostname.match(/[^\.]+/g).reverse()[x], where {subdomain[0]} would represent the TLD.

Alternatively a tab title format could look like {hostname:<regex>} which would return the matches / matching groups.

Using multiple tags is already possible.

Hey,
I want enable xframe_ignore when in Kiosk mode, the reason is because of a user reporting an issue in my project here guysoft/FullPageOS#308

Do you have a way around that? Since the button is not available in kiosk mode.

Despite the regex validation check there's no error when entering and saving an invalid regex in the URL filters textbox:

Hi, do you know if it is possible to make something simular with manifest v3, or would v3 kill the needed functionality?

Implementing this feature would also take care of the open requests #8 and #14.

Example URL: https://example.com/?login=saml&email=test%40example.com with the title “Sign-In”

Example:

The tag could be {regex=”expression”} with “expression” being the RegEx to apply.

Tab title format: {title} - {protocol}://{hostnameascii} - {regex=([a-zA-Z0-9._-]+%40([a-zA-Z0-9_-]+.)+[a-zA-Z0-9_-]+)}

Result: Sign In - https://example.com/ - test%40example.com

I have URL in the format https://servername.domain.local/Word/Word/Word/#/Word/Word

In the options I have the following setup:
{title} - {protocol}://{hostname}{port}/{path}{args}

However I am only able to see the below in the tab
https://servername.domain.local/Word/Word/Word/

The part with the # and stuff after is key so really need this to be visible in tab

I did have a look through the support and reviews on the google store etc and there was a mention of this issue on Apr 4, 2015 but you responded to say you had tested and couldn't replicate.

Am I missing something in the config, or is it not possible to show the # and bits after?

Thanks

George

My rationale is available at "ThomazPom/Moz-Ext-Ignore-X-Frame-Options#20 (comment)".

Microsoft Edge is the second most used browser on the web, making the browsing experience more flexible, offering many more services for users and optimized for Windows devices.

Microsoft Edge supports Chromium extensions, and you can publish your extensions to Microsoft Edge Add-ons website with minimal code changes. Find out more here.

If you have any more queries about porting Chrome extension to Microsoft Edge or anything else, you can contact the relevant teams whose links are given here.

Let me know if this was helpful. I am happy to help you with more details.