Summary: | macOS Sonoma web apps don't correctly report `matchMedia('(display-mode: standalone)')` | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Thomas Steiner <tomac> | ||||
Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED MOVED | ||||||
Severity: | Normal | CC: | beidson, bfulgham, david_quesada, dvpdiner2, karlcow, luming_yin, steven, webkit-bug-importer | ||||
Priority: | P2 | Keywords: | InRadar | ||||
Version: | Safari 16 | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
See Also: | https://bugs.webkit.org/show_bug.cgi?id=257776 | ||||||
Attachments: |
|
Description
Thomas Steiner
2023-06-07 08:15:22 PDT
Possibly related to #257776 (exposing navigator.standalone on macOS) FWIW, `navigator.standalone` is not standardized as far as I can tell: https://developer.mozilla.org/en-US/docs/Web/API/Navigator#navigator.standalone. There's no trace at an attempt to do so in https://github.com/whatwg/html/issues?q=is%3Aissue+%28%22standalone%22+OR+%22navigator.standalone%22%29+ either. Thanks for trying out web apps on macOS. We appreciate the testing and feedback. With my Apple hat on: The cause of this particular issue in the first macOS Sonoma developer seed isn't in WebKit, but rather in Apple's hosting application. We look forward to developers continuing to try out the feature in future seeds. With my WebKit hat on: The appropriate "webkit.org bug accounting" step here is to close as invalid. I'm adjusting the status to MOVED because this is a real issue, it's just not one that can be fixed in the WebKit Open Source code. The work is being done under <rdar://problem/110403186> in the appropriate part of the system. Thanks for working on this at the relevant level then. Glad you agree it's something that needs fixing. Please also see https://github.com/w3c/manifest/issues/1092#issuecomment-1584312331 for some relevant side notes. We will update this bugzilla as soon as a beta is available with the correct behavior. Thank you for your bug report! This issue has been resolved in macOS Sonoma Beta 3 (23A5286g). |