Some things that I still want to improve: - Introduce a new simple (rawish) image format to re-encode into. (For this first draft I am using PNG) This should make it faster to decode again in the parent and more secure, because PNG and other are still complex formats and we shouldn't trust the data coming from the child. - Make sure the child sends up image data in the expected format. - Handle SVG context-fill and CSS color-scheme? - I probably should introduce a new content process type for this. - Restrict the content process to a feature set that it could reasonable require. E.g. could we maybe prevent it from video decoding etc?
Bug 1985987 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Some things that I still want to improve: - ~~Introduce a new simple (rawish) image format to re-encode into. (For this first draft I am using PNG) This should make it faster to decode again in the parent and more secure, because PNG and other are still complex formats and we shouldn't trust the data coming from the child.~~ - ~~Make sure the child sends up image data in the expected format.~~ - Handle SVG context-fill and CSS color-scheme? - I probably should introduce a new content process type for this. - Restrict the content process to a feature set that it could reasonable require. E.g. could we maybe prevent it from video decoding etc?
Some things that I still want to improve: - ~~Introduce a new simple (rawish) image format to re-encode into. (For this first draft I am using PNG) This should make it faster to decode again in the parent and more secure, because PNG and other are still complex formats and we shouldn't trust the data coming from the child.~~ - ~~Make sure the child sends up image data in the expected format.~~ - Handle SVG context-fill and CSS color-scheme? - I probably should introduce a new content process type for this. - Restrict the content process to a feature set that it could reasonable require. E.g. could we maybe prevent it from video decoding etc? - Handle a hanging remote process (Maybe automatic?)
Some things that I still want to improve: - ~~Introduce a new simple (rawish) image format to re-encode into. (For this first draft I am using PNG) This should make it faster to decode again in the parent and more secure, because PNG and other are still complex formats and we shouldn't trust the data coming from the child.~~ - ~~Make sure the child sends up image data in the expected format.~~ - Handle SVG context-fill and CSS color-scheme? - I probably should introduce a new content process type for this. - Restrict the content process to a feature set that it could reasonable require. E.g. could we maybe prevent it from video decoding etc? - Handle a hanging remote process (Maybe automatic?) - Shutdown the process when idle