Post not yet marked as solved
Is there any resolution available for this issue. I am facing this issue with AppBoundDomains and Service worker. The page doesn't load unless the application is deleted and resinstalled.
Post not yet marked as solved
I haven't heard anything back with regardless to the feedback issue or this. Can I get some indication as to what is going on?
Post not yet marked as solved
Good day, I've attached more information as well as a couple of screen recordings to the feedback ticket - FB13744621. I've also added a link to the current production version of our extension. Please review and let me know if there is anything else you need. By safari menu, I am referring to the menu that opens up when we click on AA, which gives us options to manage our extensions as well as other options. Thank you for your time and I look forward to your response
Post not yet marked as solved
hi. I've come across a UI-related bug. It's not a critical issue, but I'm curious whether it's actually a bug or an intended result. Enable Dark Mode on your device. Set Safari to single tab mode in the settings. Open the iOS browser. Switch to Private Browsing mode. When swiping up, the background of the top toolbar (including the status bar) becomes translucent, revealing the content behind it. When I turn on the 'Reduce Transparency' setting, the issue does not occur, and the background content remains hidden as expected. iPhone12 mini / iOS 17.0.1 thx!
Post not yet marked as solved
If I set an input text box connected to a datalist-options, in order to suggest pre-coded values, this is what happens: The text field shows properly. When I start typing, one or more coincident options from the datalist are shown at the bottom of the available screen. When one option is selected, the data contained in it is NOT transcript to the input field. The same webtest works fine on Ipad mini w/ios 15. Try this simple code, it doesn't work: Choose your browser from the list:
Post not yet marked as solved
Seems to be a bug in Webkit that'll be fixed in some future release (either another 17.4.x release, or 17.5) https://bugs.webkit.org/show_bug.cgi?id=269846
Post not yet marked as solved
Thank you for filing this feedback! Is it possible to include a sample extension in the feedback that reproduces this issue + steps to reproduce using that extension? What do you mean by the Safari menu here?
Post not yet marked as solved
Same problem, fix this please!
Post not yet marked as solved
I have tested on the ios 17.5 beta version and we are still experiencing issues. Here is the feedback id: FB13744621. Here is the issue we are now facing on the 17.5 beta version. Based on our logs, what we seeing is that the content scripts are being loaded on this beta version but an issue we now seeing is that most of the time our background scripts are only getting run once we interact with our extension via the safari menu. An example of this is, our extension when landing on certain sites and the tab gets loaded we send a message from the background script to the content script to load our popups, what is happening on this version is that even though the tab has completed loading our popup wont appear until we open the safari menu and interact with our extension, as soon as we interact with the safari menu our popups get loaded and we can see the logs from our background script. This functionality used to work as expected on iOS versions prior to 17.4.1
Post not yet marked as solved
Hello We received frequent crashes for the webkit on 17.4.1. We checked the code as well nothing got changed from our side. I tried to reproduce it but unable to do so. Can anybody advice on this. Below is the stack trace for same Please help to check. Thanks in advance
Post not yet marked as solved
We believe that this issue is resolved in iOS 17.5, please test against the latest developer seed to see if your extension still experiences this issue. If it does, please let us know using http://feedbackassistant.apple.com/ and share the Feedback ID here.
Post not yet marked as solved
I would like to specify Connection: close for a request that I load in WKWebView - which actually CAN be done by setting the value on the request that is loaded (and it actually works). However, the documentation at https://developer.apple.com/documentation/foundation/nsurlrequest#1776617 states that it shouldn't be used because the URL loading system handles persistent connections for you. So - my question is how can I indicate to the URL Loading System that I do NOT want to use persistent connections for this particular request? Or - am I safe to just set the header even though it's listed as reserved (because - as mentioned - it does work)?
Post not yet marked as solved
Since updating to iOS v17.4.1 our safari extension no longer functions as it used to We are experiencing issues where our content script is not getting initialized, On devices running iOS 17.4.1, the content script included in our extension does not appear to run. There are no logs from the content script in the console, whereas on other versions and devices, it operates as expected. Our Extension relies con communication between the background and content scripts in order for us to render various popups to our users, based on our logs as of iOS 17.4.1 this communication is not successful, we can see messages being sent from the background script but as mentioned above nothing on the content script side. This behavior happens majority of the time and on random sites, sometimes opening the same site in a new tab would work but not always. There are also times where we would only receive our popups after opening the safari menu and interacting with our extension via this menu. Please assist with a way forward
Post not yet marked as solved
I'm not sure if I just missed a recent breaking change, but we are having an issue with the camera in our single page app on iOS 17.4.1 in Safari. We can open the camera and display it to the user using getUserMedia. However, if the path of the site changes at all (for example, the user clicks a button to opens a sidepanel which results in the path in the browser changing) the camera goes black, even if the video element is still being displayed. I can see in the browser that the camera has stopped, and the user has to re-enable it manually by tapping Start Using Camera. Any idea's what could be going on here?
