Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2174563 Information from BlockerBugs App: <img alt="2174563" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2174563" />
Commented but haven't voted yet: coremodule
The votes have been last counted at 2023-03-27 21:24 UTC and the last processed comment was #comment-848697
To learn how to vote, see: https://pagure.io/fedora-qa/blocker-review A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)
BetaBlocker +1
BetaBlocker
FinalBlocker
BetaFE
FinalFE
0Day
PreviousRelease
+1
0
-1
I agree with the nominating comment. If we're going to offer a virtual keyboard, it should work.
yeah, I believe we've taken critical issues in the GNOME OSK as blockers before. It's important to a11y and touchscreen use cases.
This is a show stopper for some multimedia setups with touch.
AGREED AcceptedBetaBlocker
The following votes have been closed:
AGREED RejectedBetaBlocker AGREED AcceptedFinalBlocker
Discussed during the 2023-03-06 blocker review meeting: [0]
The decision to classify this bug as a "RejectedBlocker (Beta)" and an "AcceptedBlocker (Final)" was made as discussion on this bug brought up that the virtual keyboard does work in the case where no physical keyboard is connected, so there is only a problem when a physical keyboard is connected but the user cannot or does not want to use it. We agreed this is acceptable for Beta but should still block Final.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2023-03-06/f38-blocker-review.2023-03-06-17.00.txt
With the last update Marc submitted, with Nates patch, the button have gone. I think its a valid workarround for this release.
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F38 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.