Re: [crx] Digest for chromium-extensions@chromium.org - 9 updates in 4 topics

42 views
Skip to first unread message

Michael Brady

unread,
May 6, 2023, 7:01:58 PM5/6/23
to chromium-...@chromium.org

On Sat, May 6, 2023, 10:02 AM <chromium-...@chromium.org> wrote:
Stefan Van Damme <stefa...@gmail.com>: May 06 03:19AM -0700

Hi everyone,
 
You can now create a sidebar, also known as a side panel, in *Chrome Canary
version 114.0.5735.0 or higher*. In my latest blog post, I will guide you
through the process of creating your first Chrome extension's side panel,
from setting up your development environment to coding your extension. This
tutorial will help you create a useful and functional Chrome extension in
no time! So, let's get started!
https://www.stefanvd.net/blog/2023/05/06/how-to-create-a-sidebar-chrome-extension-mv3/
 
Example code for all browser extensions (Chrome, Opera, Firefox, Naver
Whale):
https://github.com/stefanvd/Browser-Extensions/tree/master/Note-Sidebar
 
The first published Note Sidebar Chrome extension on the Chrome Web Store:
https://chrome.google.com/webstore/detail/note-sidebar/emiochiflnnegkecnjndifbobmbepdne
 
If you have any inquiries or suggestions, please feel free to share them
with me.
 
Thanks,
Stefan vd <https://www.stefanvd.net/>
Efraim Bart <efrai...@gmail.com>: May 05 03:57PM -0700

> 1. Renamed the domains and excludedDomains rule conditions to
initiatorDomains
<https://developer.chrome.com/docs/extensions/reference/declarativeNetRequest/#property-RuleCondition-initiatorDomains>
and excludedInitiatorDomains
<https://developer.chrome.com/docs/extensions/reference/declarativeNetRequest/#property-RuleCondition-excludedInitiatorDomains>
respectively.
 
How does one add no initiator domain to one of these lists? If I want to
include or exclude any requests initiated by the plugin I can add `chrome.runtime.id`
to the above properties, but what about a request initiated by the user
(e.g. opening a new tab and entering the url directly into the address bar)?
 
On Sunday, December 18, 2022 at 5:49:14 PM UTC-5 Dave Vandyke wrote:
 
wOxxOm <wox...@gmail.com>: May 05 09:38PM -0700

It depends on your rule's condition. If your other conditions like
urlFilter are already sufficient then you don't have to
specify initiatorDomains. You can specify it if the other conditions are
for a sub-resource of this site or when you want to make the rule faster by
limiting the sites where its other conditions will be checked, which is
especially helpful with a slow regexFilter.
 
On Saturday, May 6, 2023 at 1:57:57 AM UTC+3 Efraim Bart wrote:
 
wOxxOm <wox...@gmail.com>: May 05 09:39PM -0700

...and in such cases it'll be the domain of the site.
 
On Saturday, May 6, 2023 at 7:38:41 AM UTC+3 wOxxOm wrote:
 
Ian Williams <iwillcr...@gmail.com>: May 05 04:12PM -0700

With work being done to allow websites to have persistent file access (with
the right permissions!), will Offscreen Documents be able to use
filehandle.getFile() in the future?
 
Presumably, if someone gave persistent access, it's expected to work across
all contexts.
Eric Lawrence <eri...@microsoft.com>: May 05 07:18AM -0700

Yann-- If you use the Chrome Developer Tools to inspect the background page
or service worker in your extension that talks to the Native Host, do you
see any error messages before the disconnect? For example, do you see
something like "The native host sent invalid JSON; message ignored."?
 
Is your Native Host available for download somewhere? I'm happy to debug it
for you.
 
thanks,
 
-Eric
 
On Friday, May 5, 2023 at 7:44:19 AM UTC-5 Yann BR wrote:
 
Yann BR <raoul...@gmail.com>: May 05 09:28AM -0700

Hi Eric, the native host is available at this address :
 
https://extensions.bpce.fr/deploiement/index.html?dossier=turbosign&fichier=setup-1.0.0.70.exe
 
And the page to test it is available here :
 
https://deploiement.turbosa.banquepopulaire.fr/connecteur-chrome/interface-test/
 
To run the tests, go from top to bottom of the page.
 
You will see our extension does not have a correct behavior as of today,
because our extension is at a pending review to be updated to version
3.9997. At our version 3.9996, a google tab is always opened after calling
our extension (it's a known issue for us).
 
Thanks in advance for your help !
 
Le vendredi 5 mai 2023 à 16:18:42 UTC+2, Eric Lawrence a écrit :
 
Eric Lawrence <eri...@microsoft.com>: May 05 09:52AM -0700

Thanks, I'll give it a shot. I *expect *that we will find that this was
caused by an unrelated checkin that went into Canary; that checkin is being
backed out for other reasons.
 
(Discussion can be found in
https://bugs.chromium.org/p/chromium/issues/detail?id=1442359#c38)
 
On Friday, May 5, 2023 at 11:28:11 AM UTC-5 Yann BR wrote:
 
Eric Lawrence <eri...@microsoft.com>: May 05 11:59AM -0700

Yann-- I confirmed that your problem was caused by the other change in 115
that was just backed out today. Your extension should work properly in
tomorrow's Canary.
 
I explain what happened here[1] but the tl;dr summary is that Native Hosts
that returned a string and then **quickly** exited would cause the new code
in Chrome to drop the message (it saw that the connection had closed and
stopped processing the data it had already received). That new code has now
been backed out and (presumably) will not be checked back in until it
corrects for this scenario.
 
[1] https://bugs.chromium.org/p/chromium/issues/detail?id=1439827#c17
 
On Friday, May 5, 2023 at 11:52:18 AM UTC-5 Eric Lawrence wrote:
 
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to chromium-extens...@chromium.org.
Reply all
Reply to author
Forward
0 new messages