Fail in ContentParent::RecvFindImageText() on unsupported configurations
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox121 | --- | fixed |
People
(Reporter: mccr8, Assigned: mccr8)
References
(Blocks 2 open bugs)
Details
(Keywords: sec-want, Whiteboard: [adv-main121-])
Attachments
(1 file)
It would be good to reject this message immediately in ContentParent::RecvFindImageText() if we're in a configuration that doesn't support it (eg if the pref is false or the platform doesn't support it). The stub implementation of the image text finder looks harmless but better safe than sorry. Though that might require adjusting test_image_recognition_unsupported.html.
Updated•2 years ago
|
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Comment 1•2 years ago
|
||
Also, avoid calling SendFindImageText() on unsupported platforms, so that
test_image_recognition_unsupported.html will pass.
| Assignee | ||
Comment 2•2 years ago
|
||
I've only tested this on MacOS, but I messed around with it enough that I think I properly tested what will happen on unsupported systems. test_image_recognition_unsupported.html should still pass. If we do send the message somehow, we'll crash the child process or whatever the IPC fail does.
Comment 4•2 years ago
|
||
| bugherder | ||
Comment 5•2 years ago
|
||
| bugherder | ||
Updated•2 years ago
|
Description
•