(In reply to Dale Harvey (:daleharvey) from comment #3)
This happens with QuickActions but it could conceivably happen with other UrlbarProviders if they were to show some type of notice without anything actionable contained (I dont think there are any at the moment, but it seems like something that could feasibly happen).
I don't know, an unselectable row seems like an odd concept for what is essentially still an autocomplete UI. I think if we want to add notices we should have an API for that rather than mixing this in with results.
Do you foresee any issues with reintroducing a check before selecting a row to check whether the row is a dynamicResult with no selectable buttons and if so skipping selection of that row?
Well yes, the code I linked to isn't prepared for that because it deals with rows rather than selectable elements. I'm sure something could be hacked together, but it wasn't obvious to me when looking into this and the result may be messy. So given my skepticism about the concept of unselectable rows, I remain reluctant to go down that path.
That seems the ideal solution, but if you see technical / ux problems with that then I think this will have to go to UX, not having quickactions return any items in that case is doable but I would be worried the inconsistent behaviour would be confusing
It seems confusing either way. I certainly didn't understand why I was offered the disabled screenshot action.
(In reply to Donal Meehan [:dmeehan] from comment #4)
:dao this is the final week of 111 nightly, 111 goes to beta next week.
Could this be triaged?
QuickActions are only enabled in Nightly and Early Beta, so I think we're okay for now. Dale, is there a timeline for letting QuickActions ride a release train?