What would you consider "done right"? The main problem with it was that they used it on a desktop computer operating system. I'm sure it was just fine on Windows Phone.
2xsaiko
joined 2 years ago
Round 2 :)
This one is very annoying when I have Safari windows already open on my secondary display and trying to create a new Safari window on my primary display because it then needs an extra click to focus the window.
Since this occurs with multiple apps (and also third-party ones like BBEdit), this is very likely not an issue in each of the apps but rather in AppKit or the windowing system.
FB17088400 Opening a new window of various apps via the Dock icon while the app is inactive does not focus it when it is created on another display
Normally, opening a new window of an app that supports this via the dock icon (e.g. Finder, Terminal, Safari) focuses the newly created window. However, this does not work correctly when the app is not focused and the previously focused window of the app is on a different display. In that case, it will create the new window on the current display, but keep the previously focused window focused.
This does not happen if either the app creating the new window is already active, or there are no windows of that app, or the previously active window is on the same display as the new window is created from using the Dock.
I’ve found this issue to occur in the following apps:
- Finder
- Terminal
- Safari
- TextEdit
- QuickTime Player
To reproduce:
- Have at least two displays connected
- Open Terminal (or any other app of the list above) with at least one open window
- Focus another app (e.g. Finder’s desktop) on the display the Terminal window is not on
- Control-click on Terminal’s dock icon on that display
- Select “New Window”
Observed result: Terminal creates a new window, but does not focus it. Instead, the last focused Terminal window is activated.
Expected result: The newly created window is always focused (and appears on the display the Dock was used from).
System info:
- MacBook Air M2, 2022, 8GB RAM, 256GB storage
- macOS 15.3.2 (24D81)
8 points! 8, 9, 12, 13, 14, 17, 19, 20
Seeing your characters on this is the icing on the cake :)
Also face with bag under eyes . Instant classic
Oh hey, awesome!
I'll just paste here what I've already written in Feedback Assistant.
FB15922287 Messages sometimes only allows you to send SMS despite the recipient supporting RCS
- Device: any
- App: Messages
- Conversation type: 1-on-1, RCS
Sometimes, Messages only allows you to send SMS despite the recipient supporting RCS. During a conversation, receiving an RCS message even briefly changes the text in the input bar to RCS before switching back to SMS.
This seems to be caused by failing to deliver an RCS message sometime before, which can always happen (bad connection on either side, recipient is offline, other network error, etc.)
To reproduce:
- Take recipient phone offline
- Send an RCS message
- Wait for it to fail to be delivered
- Take recipient phone online
Observed result: Messages shows the recipient as supporting SMS only, ~~even when they are actively sending you RCS messages.~~
Expected result: RCS is never artificially disallowed by Messages.
This also happens if you use the “Send as SMS” entry in the context menu on a stuck message.
Looks like at this point receiving an RCS message fixes this. However one sent RCS message that falls back to SMS will still lock the conversation to SMS until you get a reply.
FB16920262 Separate window for single conversation does not mark messages as read
- Device: Mac
- App: Messages
- Conversation type: 1-on-1, RCS (probably any)
When opening a conversation in a new window, this window does not mark the messages as read when active like the main window.
To reproduce:
- Open conversation in new window (Control click on conversation, Open in New Window)
- Receive a message
- Focus the separate window/scroll to the bottom
Observed result: The received message is not marked as read
Expected result: The received message is marked as read like in the main window
FB17053263 When "Group windows by application" is enabled, selecting a specific window from Mission Control does not actually focus the window
- Device: Mac
- App: Mission Control
In Mission Control, with the "Group windows by application" setting enabled, you can scroll up to unstack the windows of an application to allow you to select a specific one. In this view, clicking one of them focuses the application but not the window, leading to a weird state where the application is focused but none of its windows are, and the menu bar also isn't interactible until you click on another window.
Steps to reproduce:
- Turn on "Group windows by application" in System Settings (Desktop & Dock)
- Open an application such as TextEdit, open one or multiple windows
- Open Mission Control
- Scroll up on the TextEdit group to expand its windows
- Click one of the TextEdit windows
Observed result: The application is focused but none of its windows are, nor are they ordered to front. This also looks really glitchy because Mission Control will show the animation that the selected window is expected to be in front but it will then move back behind any other windows that were in front of it after the animation is done
Expected result: The selected window is focused and ordered to front, like when you don’t scroll up.
System info:
- MacBook Air M2, 2022, 8GB RAM, 256GB storage
- macOS 15.3.2 (24D81)
- iPhone 13 mini, 128GB storage
- iOS 18.3.2 (22D82)
I have a couple more watchOS ones, and a couple wonky ones that I either don't know how to reliably reproduce, or can't reproduce anymore right now but also don't know if they're fixed yet. But these should be the bugs I can think of right now that I can reliably reproduce that aren't watchOS. If I find/remember more I'll post them.
This also just made me check and close 2 feedbacks that did get fixed in the meantime :^)
Ventoy is completely insane in terms of how it works fwiw: https://discourse.nixos.org/t/custom-nixos-installer-plug-install-play-how-to-achieve-this/61710/13
It's certainly not a universal thing either, no other language I know does it.
Once I asked on linguistics (or maybe English language) stackexchange about the origins of it, but it got deleted as duplicate of a related but definitely different question. Most satisfying stackexchange interaction
Generally there are no shortcuts with option as the only modifier on keys that actually type characters (for this reason I suppose), usually command+option+something or non-symbol keys such as option+up. Use command+option+number instead.
There are many shortcuts using Option as a modifier. Probably the second most common one after Command. What do you mean it cannot be used as a modifier?
Eh, works for me for home use. I just have it running on the same machine as the NFS server. The only thing that bothers me is that I can’t use normal Kerberos for SMB, I’d have to set up Samba AD. Boooo
I even managed to make it work with just mDNS as I’m currently in a horrible network I don’t control.
Yes, let’s