#feedbackassistant โ Public Fediverse posts
Live and recent posts from across the Fediverse tagged #feedbackassistant, aggregated by home.social.
-
For my own reference, the watchOS bug where simply going into the face switching view stops the ability to scroll the digital crown to open the Smart Stack and Notifications:
FB22790238
(100% reliably reproducible for me, still happening in watchOS 26.5, seemingly only affects Hermรจs models, but it may not be exclusive to those models and might be a particular combination of faces or settings)
-
For my own reference, the watchOS bug where simply going into the face switching view stops the ability to scroll the digital crown to open the Smart Stack and Notifications:
FB22790238
(100% reliably reproducible for me, still happening in watchOS 26.5, seemingly only affects Hermรจs models, but it may not be exclusive to those models and might be a particular combination of faces or settings)
-
For my own reference, the watchOS bug where simply going into the face switching view stops the ability to scroll the digital crown to open the Smart Stack and Notifications:
FB22790238
(100% reliably reproducible for me, still happening in watchOS 26.5, seemingly only affects Hermรจs models, but it may not be exclusive to those models and might be a particular combination of faces or settings)
-
For my own reference, the watchOS bug where simply going into the face switching view stops the ability to scroll the digital crown to open the Smart Stack and Notifications:
FB22790238
(100% reliably reproducible for me, still happening in watchOS 26.5, seemingly only affects Hermรจs models, but it may not be exclusive to those models and might be a particular combination of faces or settings)
-
RE: https://mastodon.social/@eurozerozero/109545343867263500
It has taken years and several attempts, but it looks like this bug with Safariโs Web Inspector (which I would run into every day!) might now actually be fixed in Safari Technology Preview 243. Hereโs the commit that also details the race condition that caused it:
https://github.com/WebKit/WebKit/commit/34544098f193a69078e4b6458d8bdfd2e17b65a3
FB11886541 โ
#WebInspector #Safari #SafariTechnologyPreview #WebKit #FeedbackAssistant
-
RE: https://mastodon.social/@eurozerozero/109545343867263500
It has taken years and several attempts, but it looks like this bug with Safariโs Web Inspector (which I would run into every day!) might now actually be fixed in Safari Technology Preview 243. Hereโs the commit that also details the race condition that caused it:
https://github.com/WebKit/WebKit/commit/34544098f193a69078e4b6458d8bdfd2e17b65a3
FB11886541 โ
#WebInspector #Safari #SafariTechnologyPreview #WebKit #FeedbackAssistant
-
RE: https://mastodon.social/@eurozerozero/109545343867263500
It has taken years and several attempts, but it looks like this bug with Safariโs Web Inspector (which I would run into every day!) might now actually be fixed in Safari Technology Preview 243. Hereโs the commit that also details the race condition that caused it:
https://github.com/WebKit/WebKit/commit/34544098f193a69078e4b6458d8bdfd2e17b65a3
FB11886541 โ
#WebInspector #Safari #SafariTechnologyPreview #WebKit #FeedbackAssistant
-
RE: https://mastodon.social/@eurozerozero/109545343867263500
It has taken years and several attempts, but it looks like this bug with Safariโs Web Inspector (which I would run into every day!) might now actually be fixed in Safari Technology Preview 243. Hereโs the commit that also details the race condition that caused it:
https://github.com/WebKit/WebKit/commit/34544098f193a69078e4b6458d8bdfd2e17b65a3
FB11886541 โ
#WebInspector #Safari #SafariTechnologyPreview #WebKit #FeedbackAssistant
-
๐ญ๐ผ ๐ธ๐๐ป ๐ท๐ฒ ๐ฏ๐๐ด๐ ๐บ๐ฒ๐น๐ฑ๐ฒ๐ป ๐ฏ๐ถ๐ท ๐๐ฝ๐ฝ๐น๐ฒ: ๐ฎ๐น๐น๐ฒ๐ ๐ผ๐๐ฒ๐ฟ ๐๐ฒ๐ฒ๐ฑ๐ฏ๐ฎ๐ฐ๐ธ ๐๐๐๐ถ๐๐๐ฎ๐ป๐
Heb je een bug ontdekt in een van de beta's en wil je dit melden aan Apple, dan kan dat op verschillende manieren. In deze tip lees je hoe je bugs kunt melden bij Apple via de Bug Reporter, Feedback Assistant en tools van derden. Daarnaast bespreken we wat je kunt doen als je een fout hebt...
-
๐ญ๐ผ ๐ธ๐๐ป ๐ท๐ฒ ๐ฏ๐๐ด๐ ๐บ๐ฒ๐น๐ฑ๐ฒ๐ป ๐ฏ๐ถ๐ท ๐๐ฝ๐ฝ๐น๐ฒ: ๐ฎ๐น๐น๐ฒ๐ ๐ผ๐๐ฒ๐ฟ ๐๐ฒ๐ฒ๐ฑ๐ฏ๐ฎ๐ฐ๐ธ ๐๐๐๐ถ๐๐๐ฎ๐ป๐
Heb je een bug ontdekt in een van de beta's en wil je dit melden aan Apple, dan kan dat op verschillende manieren. In deze tip lees je hoe je bugs kunt melden bij Apple via de Bug Reporter, Feedback Assistant en tools van derden. Daarnaast bespreken we wat je kunt doen als je een fout hebt...
-
๐ญ๐ผ ๐ธ๐๐ป ๐ท๐ฒ ๐ฏ๐๐ด๐ ๐บ๐ฒ๐น๐ฑ๐ฒ๐ป ๐ฏ๐ถ๐ท ๐๐ฝ๐ฝ๐น๐ฒ: ๐ฎ๐น๐น๐ฒ๐ ๐ผ๐๐ฒ๐ฟ ๐๐ฒ๐ฒ๐ฑ๐ฏ๐ฎ๐ฐ๐ธ ๐๐๐๐ถ๐๐๐ฎ๐ป๐
Heb je een bug ontdekt in een van de beta's en wil je dit melden aan Apple, dan kan dat op verschillende manieren. In deze tip lees je hoe je bugs kunt melden bij Apple via de Bug Reporter, Feedback Assistant en tools van derden. Daarnaast bespreken we wat je kunt doen als je een fout hebt...
-
๐ญ๐ผ ๐ธ๐๐ป ๐ท๐ฒ ๐ฏ๐๐ด๐ ๐บ๐ฒ๐น๐ฑ๐ฒ๐ป ๐ฏ๐ถ๐ท ๐๐ฝ๐ฝ๐น๐ฒ: ๐ฎ๐น๐น๐ฒ๐ ๐ผ๐๐ฒ๐ฟ ๐๐ฒ๐ฒ๐ฑ๐ฏ๐ฎ๐ฐ๐ธ ๐๐๐๐ถ๐๐๐ฎ๐ป๐
Heb je een bug ontdekt in een van de beta's en wil je dit melden aan Apple, dan kan dat op verschillende manieren. In deze tip lees je hoe je bugs kunt melden bij Apple via de Bug Reporter, Feedback Assistant en tools van derden. Daarnaast bespreken we wat je kunt doen als je een fout hebt...
-
๐ฅด Oh, the joys of bug reporting with Apple: it's like playing whack-a-mole where the moles gaslight you into thinking they're fixed unless you constantly babysit them. Developers suggest boycotting the Feedback Assistant โ but who can resist the thrill of shouting into the void, hoping for a miracle? ๐คช๐ง
https://lapcatsoftware.com/articles/2026/3/11.html #bugreporting #Apple #FeedbackAssistant #developerstruggles #softwarebugs #techhumor #HackerNews #ngated -
๐ฅด Oh, the joys of bug reporting with Apple: it's like playing whack-a-mole where the moles gaslight you into thinking they're fixed unless you constantly babysit them. Developers suggest boycotting the Feedback Assistant โ but who can resist the thrill of shouting into the void, hoping for a miracle? ๐คช๐ง
https://lapcatsoftware.com/articles/2026/3/11.html #bugreporting #Apple #FeedbackAssistant #developerstruggles #softwarebugs #techhumor #HackerNews #ngated -
๐ฅด Oh, the joys of bug reporting with Apple: it's like playing whack-a-mole where the moles gaslight you into thinking they're fixed unless you constantly babysit them. Developers suggest boycotting the Feedback Assistant โ but who can resist the thrill of shouting into the void, hoping for a miracle? ๐คช๐ง
https://lapcatsoftware.com/articles/2026/3/11.html #bugreporting #Apple #FeedbackAssistant #developerstruggles #softwarebugs #techhumor #HackerNews #ngated -
๐ฅด Oh, the joys of bug reporting with Apple: it's like playing whack-a-mole where the moles gaslight you into thinking they're fixed unless you constantly babysit them. Developers suggest boycotting the Feedback Assistant โ but who can resist the thrill of shouting into the void, hoping for a miracle? ๐คช๐ง
https://lapcatsoftware.com/articles/2026/3/11.html #bugreporting #Apple #FeedbackAssistant #developerstruggles #softwarebugs #techhumor #HackerNews #ngated -
๐ฅด Oh, the joys of bug reporting with Apple: it's like playing whack-a-mole where the moles gaslight you into thinking they're fixed unless you constantly babysit them. Developers suggest boycotting the Feedback Assistant โ but who can resist the thrill of shouting into the void, hoping for a miracle? ๐คช๐ง
https://lapcatsoftware.com/articles/2026/3/11.html #bugreporting #Apple #FeedbackAssistant #developerstruggles #softwarebugs #techhumor #HackerNews #ngated -
Also, does the Safari Web Inspector not understand nested CSS syntax, or is the red syntax highlighting colour an intentional choice for nested rules? Because having this displayed in red sure suggests that itโs invalid syntax.
(I can only assume it doesnโt understand nesting because thereโs also no way to edit nested rules directly in the Styles pane of the Elements tab)
WebKit/Safari team: FB21689793
-
Also, does the Safari Web Inspector not understand nested CSS syntax, or is the red syntax highlighting colour an intentional choice for nested rules? Because having this displayed in red sure suggests that itโs invalid syntax.
(I can only assume it doesnโt understand nesting because thereโs also no way to edit nested rules directly in the Styles pane of the Elements tab)
WebKit/Safari team: FB21689793
-
Also, does the Safari Web Inspector not understand nested CSS syntax, or is the red syntax highlighting colour an intentional choice for nested rules? Because having this displayed in red sure suggests that itโs invalid syntax.
(I can only assume it doesnโt understand nesting because thereโs also no way to edit nested rules directly in the Styles pane of the Elements tab)
WebKit/Safari team: FB21689793
-
Also, does the Safari Web Inspector not understand nested CSS syntax, or is the red syntax highlighting colour an intentional choice for nested rules? Because having this displayed in red sure suggests that itโs invalid syntax.
(I can only assume it doesnโt understand nesting because thereโs also no way to edit nested rules directly in the Styles pane of the Elements tab)
WebKit/Safari team: FB21689793
-
While working with the dialog element over the past week I keep seeing this Safari Web Inspector bug:
Having a nested @ starting-style rule within dialog::backdrop causes the Web Inspector to display the wrong style definitions when inspecting elements within a dialog element.
e.g. inspecting a button inside a form in the dialog shows the formโs styles as the buttonโs styles, an off-by-one type bug.
WebKit/Safari team: FB21689457
-
While working with the dialog element over the past week I keep seeing this Safari Web Inspector bug:
Having a nested @ starting-style rule within dialog::backdrop causes the Web Inspector to display the wrong style definitions when inspecting elements within a dialog element.
e.g. inspecting a button inside a form in the dialog shows the formโs styles as the buttonโs styles, an off-by-one type bug.
WebKit/Safari team: FB21689457
-
While working with the dialog element over the past week I keep seeing this Safari Web Inspector bug:
Having a nested @ starting-style rule within dialog::backdrop causes the Web Inspector to display the wrong style definitions when inspecting elements within a dialog element.
e.g. inspecting a button inside a form in the dialog shows the formโs styles as the buttonโs styles, an off-by-one type bug.
WebKit/Safari team: FB21689457
-
While working with the dialog element over the past week I keep seeing this Safari Web Inspector bug:
Having a nested @ starting-style rule within dialog::backdrop causes the Web Inspector to display the wrong style definitions when inspecting elements within a dialog element.
e.g. inspecting a button inside a form in the dialog shows the formโs styles as the buttonโs styles, an off-by-one type bug.
WebKit/Safari team: FB21689457
-
Feedback filed (FB21466091) - macOS 26.2
Unable to disable widgets on headless Mac being connected to via screen sharing. Didn't try a reboot, but relaunch of finder, disconnect/reconnect via screen sharing tried.
-
Feedback filed (FB21466091) - macOS 26.2
Unable to disable widgets on headless Mac being connected to via screen sharing. Didn't try a reboot, but relaunch of finder, disconnect/reconnect via screen sharing tried.
-
Feedback filed (FB21466091) - macOS 26.2
Unable to disable widgets on headless Mac being connected to via screen sharing. Didn't try a reboot, but relaunch of finder, disconnect/reconnect via screen sharing tried.
-
Feedback filed (FB21466091) - macOS 26.2
Unable to disable widgets on headless Mac being connected to via screen sharing. Didn't try a reboot, but relaunch of finder, disconnect/reconnect via screen sharing tried.
-
Feedback filed (FB21466091) - macOS 26.2
Unable to disable widgets on headless Mac being connected to via screen sharing. Didn't try a reboot, but relaunch of finder, disconnect/reconnect via screen sharing tried.
-
Hey Apple engineers, Iโve now got a sysdiagnose that should capture this serious excessive CPU usage issue with Pages, corespotlightd, fileproviderd, com.apple.CloudDocs.iCloudDriveFileProvider, tccd, etc that occurs when shared Pages documents stored on iCloud Drive are left open in the background.
FB21369001
It is happening again today and is starting to become very annoying, because it kills battery life.
-
Hey Apple engineers, Iโve now got a sysdiagnose that should capture this serious excessive CPU usage issue with Pages, corespotlightd, fileproviderd, com.apple.CloudDocs.iCloudDriveFileProvider, tccd, etc that occurs when shared Pages documents stored on iCloud Drive are left open in the background.
FB21369001
It is happening again today and is starting to become very annoying, because it kills battery life.
-
Hey Apple engineers, Iโve now got a sysdiagnose that should capture this serious excessive CPU usage issue with Pages, corespotlightd, fileproviderd, com.apple.CloudDocs.iCloudDriveFileProvider, tccd, etc that occurs when shared Pages documents stored on iCloud Drive are left open in the background.
FB21369001
It is happening again today and is starting to become very annoying, because it kills battery life.
-
Hey Apple engineers, Iโve now got a sysdiagnose that should capture this serious excessive CPU usage issue with Pages, corespotlightd, fileproviderd, com.apple.CloudDocs.iCloudDriveFileProvider, tccd, etc that occurs when shared Pages documents stored on iCloud Drive are left open in the background.
FB21369001
It is happening again today and is starting to become very annoying, because it kills battery life.
-
Hey Apple engineers, Iโve now got a sysdiagnose that should capture this serious excessive CPU usage issue with Pages, corespotlightd, fileproviderd, com.apple.CloudDocs.iCloudDriveFileProvider, tccd, etc that occurs when shared Pages documents stored on iCloud Drive are left open in the background.
FB21369001
It is happening again today and is starting to become very annoying, because it kills battery life.
-
Edit: I think this is issue is fixed in Safari 26.4 beta 1! ๐
Hey Safari/WebKit engineers, hereโs a new one for you: Safari constantly repaints the contents of a background tab, causing very high CPU usage, until you switch back to the tab and it stops.
(specifically in my case, the site is app.fastmail.com @fastmail - I suspect it does a background update that triggers a repaint/relayout and that gets stuck in a loop)
FB21368897
-
Edit: I think this is issue is fixed in Safari 26.4 beta 1! ๐
Hey Safari/WebKit engineers, hereโs a new one for you: Safari constantly repaints the contents of a background tab, causing very high CPU usage, until you switch back to the tab and it stops.
(specifically in my case, the site is app.fastmail.com @fastmail - I suspect it does a background update that triggers a repaint/relayout and that gets stuck in a loop)
FB21368897
-
Edit: I think this is issue is fixed in Safari 26.4 beta 1! ๐
Hey Safari/WebKit engineers, hereโs a new one for you: Safari constantly repaints the contents of a background tab, causing very high CPU usage, until you switch back to the tab and it stops.
(specifically in my case, the site is app.fastmail.com @fastmail - I suspect it does a background update that triggers a repaint/relayout and that gets stuck in a loop)
FB21368897
-
Edit: I think this is issue is fixed in Safari 26.4 beta 1! ๐
Hey Safari/WebKit engineers, hereโs a new one for you: Safari constantly repaints the contents of a background tab, causing very high CPU usage, until you switch back to the tab and it stops.
(specifically in my case, the site is app.fastmail.com @fastmail - I suspect it does a background update that triggers a repaint/relayout and that gets stuck in a loop)
FB21368897
-
#FeedbackAssistant #macOSTahoe
Filed FB20661489 "Reveal folder" does open Finder window with correct path, but doesn't make it frontmost
This is quite confusing. You click "Reveal in Finder" somewhere, a window opens, you start typing, butโฆ you can't.
-
#FeedbackAssistant #macOSTahoe
Filed FB20661489 "Reveal folder" does open Finder window with correct path, but doesn't make it frontmost
This is quite confusing. You click "Reveal in Finder" somewhere, a window opens, you start typing, butโฆ you can't.
-
#FeedbackAssistant #macOSTahoe
Filed FB20661489 "Reveal folder" does open Finder window with correct path, but doesn't make it frontmost
This is quite confusing. You click "Reveal in Finder" somewhere, a window opens, you start typing, butโฆ you can't.
-
#FeedbackAssistant #macOSTahoe
Filed FB20661489 "Reveal folder" does open Finder window with correct path, but doesn't make it frontmost
This is quite confusing. You click "Reveal in Finder" somewhere, a window opens, you start typing, butโฆ you can't.
-
#FeedbackAssistant #macOSTahoe
Filed FB20661489 "Reveal folder" does open Finder window with correct path, but doesn't make it frontmost
This is quite confusing. You click "Reveal in Finder" somewhere, a window opens, you start typing, butโฆ you can't.
-
@karlcow Hi Karl, just letting you know that this bug is still there in Safari 26 and Iโve filed a fresh bug report, FB20644457. Itโd be great if you could get someone to look at it. Although the bug has been there for at least three years, itโs now happening so frequently that itโs almost impossible for me to use Safari for web development.
The report includes a screen recording, reproduction steps, etc.
This is also reproducible in the latest STP Release 229.
-
@karlcow Hi Karl, just letting you know that this bug is still there in Safari 26 and Iโve filed a fresh bug report, FB20644457. Itโd be great if you could get someone to look at it. Although the bug has been there for at least three years, itโs now happening so frequently that itโs almost impossible for me to use Safari for web development.
The report includes a screen recording, reproduction steps, etc.
This is also reproducible in the latest STP Release 229.
-
@karlcow Hi Karl, just letting you know that this bug is still there in Safari 26 and Iโve filed a fresh bug report, FB20644457. Itโd be great if you could get someone to look at it. Although the bug has been there for at least three years, itโs now happening so frequently that itโs almost impossible for me to use Safari for web development.
The report includes a screen recording, reproduction steps, etc.
This is also reproducible in the latest STP Release 229.
-
@karlcow Hi Karl, just letting you know that this bug is still there in Safari 26 and Iโve filed a fresh bug report, FB20644457. Itโd be great if you could get someone to look at it. Although the bug has been there for at least three years, itโs now happening so frequently that itโs almost impossible for me to use Safari for web development.
The report includes a screen recording, reproduction steps, etc.
This is also reproducible in the latest STP Release 229.
-
@karlcow Hi Karl, just letting you know that this bug is still there in Safari 26 and Iโve filed a fresh bug report, FB20644457. Itโd be great if you could get someone to look at it. Although the bug has been there for at least three years, itโs now happening so frequently that itโs almost impossible for me to use Safari for web development.
The report includes a screen recording, reproduction steps, etc.
This is also reproducible in the latest STP Release 229.
-
@dashorst Iโve reported this bug (FB20414621) and the bug report shows that there are other similar reports, so they must know about it, but I donโt think they realise just how bad it is. It still says โResolution: Openโ, too.
I really hope we donโt have to wait until theyโre ready to release Safari 26.1 because this needs a fix ASAP.
Iโve seen it allocating upwards of 120GB of RAM before it crashes. Itโs probably causing a lot of SSD wear too.