On Safari Mobile and iOS version 16 or 17, while scrolling the webpage, the function browser.tabs.captureVisibleTab() is not returning the expected screen image. The image is cropped from the top. The probable reason for the same is the collapsible Address Bar. The below attached image is the iPad mini (6th generation ) Simulator OS Version:17.0 simulator The below attached image is created by browser.tabs.captureVisibleTab() I tested it on iPad mini (6th generation ) Simulator OS Version:17.0 and iPad (8th generation) - iPadOS Version 16.2.

I'm using standard Safari Web Push, but my notifications aren't coming through. I'm trying to debug this. Is it possible to use the Apple Push Notifications Console to debug/analyze Safari Web Push deliverability? I can't figure out how to use it for web push. When I login and try to use the Push Notification Console, it asks me to choose an "app." But for standard Safari 16+ Web Push, there is no "app," no "Website Push ID", etc. that I register with Apple. So how can I use the Push Notification Console for this? Apple's documentation does strongly imply that it should work. Sending web push notifications in web apps and browsers: To resolve an error, address the issue and resend your push notification request. For more information about the factors that impact the delivery of a push notification, see Viewing the status of push notifications using Metrics and APNs. And that page is all about the Push Notification Console. So it must be possible somehow, right?

Has the Preserve Log option been moved from the Network tab in DevTools? I've just upgraded from Intel to Apple Silicon and am not finding this option on Network tab or in settings.

Hi Safari team, I am a product manager working for a large content recommendation company. Our JavaScriot SDK is running on more than 9000 leading publishers worldwide and has been certified to be aligned with global legal and privacy regulations and guidelines. We have the following problem: Since the launch of Safari 17 (in iOS, iPadOS, and MacOS) - we can see our JavaScript SDK blocked when the user uses the private browsing mode Safari 17 sometimes identifies our loading and rendering JavaSctipt files as any request/action by our domain to be a tracking activity (we see the JavaScript files in the console tagged with “Blocked connection to known tracker” log) In previous Safari versions, we only got the tracking functionality blocked, allowing our content to render We have the following questions: Can JavaScript running in Safari detect the user has the privacy mode turned on? Was there something specific in Safari 17 “Tracking Protection” functionality that now blocks content rendering on the page in addition to tracking activity? Context: We can run our JavaScript without performing any form of tracking, either directly by my domain or any other 3rd party vendor we are working with. We will render our content without performing any form of tracking or fingerprinting We are already following Apple’s iOS IDFA guidelines. Our iOS SDK, for example, detects and respects when the user opts out from sharing the IDFA on an iOS app running our code. In that case, we show our content without breaching the App Tracking Transparency framework rules. Besides sponsored content, our JavaScript SDK also powers organic recommendations for our clients. With Safari 17 blocking anything in private browsing mode, we see unfair interference with organic engagement. Please let us know if you provide guidance to allow our JavaScript SDK to render content when the user uses the private browsing mode, adhering to the privacy requirements. Thank you for helping! Omri.

on our web pages we have allowed certain sources of scripts though content-security-policy meta tag which is working fine as expected on Chrome browser and on Internet Edge. However there is a script called morosa.top when it inserted in our html page, safari is not able to block it while it was supposed to block. if this script gets executed it start taking screenshots of screen and post it to hacker. Please check this could be a potential issue. [Edited by Moderator]

Hi, after the upgrade to Safari 17 the Mouse Over text, is not popping up any more. At least not in graphics. When inspecting the Element, the <g cursor="pointer" aria=label='text..' is there, but it is not doing anything. How to activate this again? Thanks

起動しようとすると予期しない理由で終了しましたと出ます。以下がエラーのレポートです。 なにか原因がご教授してもらえればと思います。 Translated Report (Full Report Below) Process: pgAdmin 4 [1260] Path: /Users/USER/pgAdmin 4.app/Contents/MacOS/pgAdmin 4 Identifier: org.pgadmin.pgadmin4 Version: 7.5 (4280.88) Code Type: X86-64 (Translated) Parent Process: launchd [1] User ID: 501 Date/Time: 2023-11-07 21:40:06.2444 +0900 OS Version: macOS 14.1 (23B74) Report Version: 12 Anonymous UUID: A28AA79C-B419-92B4-7831-8810BBA98FFE Sleep/Wake UUID: 433BCF44-5B6D-4F1D-B638-D92BACACE00C Time Awake Since Boot: 480 seconds Time Since Wake: 79 seconds System Integrity Protection: enabled Notes: PC register does not match crashing frame (0x0 vs 0x1005101F0) Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000020 Exception Codes: 0x0000000000000001, 0x0000000000000020 Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 Terminating Process: exc handler [1260] VM Region Info: 0x20 is not in any region. Bytes before following region: 140723128958944 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START ---> mapped file 7ffca81d0000-7ffccd878000 [598.7M] r-x/r-x SM=COW ...t_id=411f6b49 Error Formulating Crash Report: PC register does not match crashing frame (0x0 vs 0x1005101F0) Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread 0 ??? 0x1005101f0 ??? 1 libsystem_platform.dylib 0x7ff813b76393 _sigtramp + 51 2 nwjs Framework 0x11e831522 0x114ead000 + 160974114 3 nwjs Framework 0x11ea4e1f0 0x114ead000 + 163189232 4 nwjs Framework 0x11eabe0db 0x114ead000 + 163647707 5 nwjs Framework 0x11b3ad51a 0x114ead000 + 105907482 6 nwjs Framework 0x11b3b58d9 0x114ead000 + 105941209 7 nwjs Framework 0x11c3444bd 0x114ead000 + 122254525 8 nwjs Framework 0x11c342c46 0x114ead000 + 122248262 9 nwjs Framework 0x11ea4fde5 0x114ead000 + 163196389 10 nwjs Framework 0x11eacac97 0x114ead000 + 163699863 11 nwjs Framework 0x11e7ffcd5 0x114ead000 + 160771285 12 nwjs Framework 0x11e7fef17 0x114ead000 + 160767767 13 nwjs Framework 0x11bea7259 0x114ead000 + 117416537 14 nwjs Framework 0x118319cb0 0x114ead000 + 54971568 15 nwjs Framework 0x11831c494 0x114ead000 + 54981780 16 nwjs Framework 0x11831c927 0x114ead000 + 54982951 17 nwjs Framework 0x118318a63 0x114ead000 + 54966883 18 nwjs Framework 0x117ebb179 0x114ead000 + 50389369 19 nwjs Framework 0x1183191c6 0x114ead000 + 54968774 20 nwjs Framework 0x11a16bf90 0x114ead000 + 86765456 21 nwjs Framework 0x11a171131 0x114ead000 + 86786353 22 nwjs Framework 0x11a16d6d0 0x114ead000 + 86771408 23 nwjs Framework 0x11a25f1da 0x114ead000 + 87761370 24 nwjs Framework 0x11a16f799 0x114ead000 + 86779801 25 nwjs Framework 0x11960f4d2 0x114ead000 + 74851538 26 nwjs Framework 0x119626a6e 0x114ead000 + 74947182 27 nwjs Framework 0x1196264a9 0x114ead000 + 74945705 28 nwjs Framework 0x1196270d5 0x114ead000 + 74948821 29 nwjs Framework 0x119680ec3 0x114ead000 + 75316931 30 nwjs Framework 0x11967da22 0x114ead000 + 75303458 31 nwjs Framework 0x1196806df 0x114ead000 + 75314911 32 CoreFoundation 0x7ff813c23a16 CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION + 17 33 CoreFoundation 0x7ff813c239b9 __CFRunLoopDoSource0 + 157 34 CoreFoundation 0x7ff813c23788 __CFRunLoopDoSources0 + 215 35 CoreFoundation 0x7ff813c223f8 __CFRunLoopRun + 919 36 CoreFoundation 0x7ff813c21a99 CFRunLoopRunSpecific + 557 37 HIToolbox 0x7ff81e9899d9 RunCurrentEventLoopInMode + 292 38 HIToolbox 0x7ff81e9897e6 ReceiveNextEventCommon + 665 39 HIToolbox 0x7ff81e989531 _BlockUntilNextEventMatchingListInModeWithFilter + 66 40 AppKit 0x7ff817193885 _DPSNextEvent + 880 41 AppKit 0x7ff817a87348 -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1304 42 nwjs Framework 0x1190b83f0 0x114ead000 + 69252080 43 nwjs Framework 0x11967da22 0x114ead000 + 75303458 44 nwjs Framework 0x1190b8369 0x114ead000 + 69251945 45 AppKit 0x7ff817184dfa -[NSApplication run] + 603 46 nwjs Framework 0x1196814ac 0x114ead000 + 75318444 47 nwjs Framework 0x11968023c 0x114ead000 + 75313724 48 nwjs Framework 0x119627459 0x114ead000 + 74949721 49 nwjs Framework 0x1195ee15f 0x114ead000 + 74715487 50 nwjs Framework 0x1174fc301 0x114ead000 + 40170241 51 nwjs Framework 0x1174fdc92 0x114ead000 + 40176786 52 nwjs Framework 0x1174f9a5a 0x114ead000 + 40159834 53 nwjs Framework 0x118a351c4 0x114ead000 + 62423492 54 nwjs Framework 0x118a36389 0x114ead000 + 62428041 55 nwjs Framework 0x118a3619d 0x114ead000 + 62427549 56 nwjs Framework 0x118a34867 0x114ead000 + 62421095 57 nwjs Framework 0x118a34b03 0x114ead000 + 62421763 58 nwjs Framework 0x114eb0930 ChromeMain + 560 59 pgAdmin 4 0x10034e87e main + 286 60 dyld 0x20041d3a6 start + 1942

I have simulators downloaded to my 14" M2 Pro Macbook Pro, and for some reason, I cannot see any simulators as an option in Safari's Responsive Design Mode. Am I missing something obvious, or is my computer bugged? Above is an image of the Responsive Design Mode showing no simulators. I would offer more screenshots to prove that I have simulators installed, but it won't let me upload any more photos for some reason.

version: iOS 16.4(20E5239a) both on my iphone and Simulator，Safari -> develop shows "no inspectable applications"

Hi there - I am trying to port over Chrome extension over to Safari Web extension. Looks like Safari has a very aggressive permissions flow which isn't a great user experience but I get the privacy benefits. I am trying to move some of my permissions like <all_urls> or tabs as optional permissions and build a flow where I can request the user for them in hopes that i can educate them as to why I need them similar to how Chrome/FF have it. However when i use browser.permissions.request - i always end up getting true without invoking the prompt. The prompt seems to come up regardless when i start visiting a website. Can someone help with this? Sounds more like a defect in Safari.