Reenable "Print Selection Only" print option in Firefox PDF viewer again
Categories
(Firefox :: PDF Viewer, enhancement)
Tracking
()
People
(Reporter: julian.viereck, Unassigned)
References
(Depends on 1 open bug)
Details
(Whiteboard: [pdfjs-feature][pdfjs-printing])
The "Print Selection Only" print option was disabled in bug #830278. Things require to enable this feature again: - Fix the OOM issue by fixing bug #839914 - (Hope that's enough) - Revert: https://bug830278.bugzilla.mozilla.org/attachment.cgi?id=710180
Updated•11 years ago
|
I just got a mail that bug. It seems that visual impairment people are running quite often in this issue, so we could also improve accessibility by fixing this.
Updated•2 years ago
|
Updated•2 years ago
|
Comment 2•2 months ago
|
||
Anna or Morgan, could you help us understand the severity of this bug for users with visual impairment?
Comment 3•2 months ago
|
||
(In reply to Marco Castelluccio [:marco] from comment #2)
Anna or Morgan, could you help us understand the severity of this bug for users with visual impairment?
I'm not familiar with this feature -- does this allow users to highlight a section and then print only the highlighted chunk?
I'm not sure why this would be an issue people with visual impairments encounter more often than other users. Maybe the codepath this was previously implemented with was an especially hot path in the a11y API? Though I don't know why that'd be true 🤔
Sorry I can't be of more help :(
Comment 4•2 months ago
|
||
(In reply to Morgan Reschenberg [:morgan] from comment #3)
(In reply to Marco Castelluccio [:marco] from comment #2)
Anna or Morgan, could you help us understand the severity of this bug for users with visual impairment?
I'm not familiar with this feature -- does this allow users to highlight a section and then print only the highlighted chunk?
Yes, you can try this on any page. Select some text, open the context menu, then "Print selection...".
I'm not sure why this would be an issue people with visual impairments encounter more often than other users. Maybe the codepath this was previously implemented with was an especially hot path in the a11y API? Though I don't know why that'd be true 🤔
Sorry I can't be of more help :(
Thanks! Removing the "access" keyword then since this is not an accessibility bug.
Description
•