microsoft
Extensions can't access edgeservices.bing.com/chat
Hey, seems like when browsing "edgeservices.bing.com/chat" on Edge, no extension content script runs on that page. Is it some kind of known limitation? Does Edge have some code to explicitly isolate that domain / URL from extensions?
Hey @eadan-y-walkme, thank you for reaching out to us.
Could you please help us with the required below details?
It will be helpful for our team to investigate.
Describe the bug A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]
Additional context Add any other context about the problem here.
@eadan-y-walkme sorry I am not clear. Are you expecting your extension to be able to access the co-pilot chat etc. or are you trying whether in the chat experience, an extension is able work.
Hey, I'm expecting my extension (and ANY extension actually) to be able to access pages under "edgeservices.bing.com/chat" domain, when browsed regularly within a browser tab, just like any other page.
@eadan-y-walkme Thanks for the feedback. Trying understand your scenario a little better. You wish to get access only the webpage for customization purposes or are you suggesting that you would like to use co-pilot APIs to create AI based capabilities?
Maybe a little more clarity on your scenario would help. Maybe you can share what do you wish to accomplish if you had access to the page.
Our product is Digital Adoption Platform, which allows for example customer to show a message to their end users when reaching certain sites (for example - "Please don't share any sensitive data with the Copilot chat"). We need our extension to be able to show such messages on the URL. Generally speaking, i'm not sure how the use case is relevant - chromium extension should have access to any web page (assuming it has permissions to it), expect chrome:// (or edge://) pages. Excluding specific URLs from inject the content scripts of extensions breaks that model. My best guess is that it was excluded from extensions because it is the same URL that is opened on the new Edge Sidebar, but when browsing the url from a regular tab - extension should work as expected.
Hey @eadan-y-walkme, could you please help us with your extension details for us to verify and assist you further.
I can try and illustrate with a demo extension but I don't think thats what youre looking for. Lets say a customer wants an extension that limits copilot usage and shows all employees a message that says "don't share any private data". We can't do that with the copilot sidebar, although it is a regular webpage.
hi, it now seems like extensions can't access copilot.microsoft.com as well, even on regular tabs. is this intended?