How will they achieve accessibility? I can only imagine screen readers trying to parse a bunch of vectors.
Google Docs will now use canvas based rendering
11–20 of 953 posts
Re: Google Docs will now use canvas based rendering
#12I don't build extensions or work on much front end web lately but this reads like Google wants more control over their stuff. The web is becoming less open. > By moving away from HTML-based rendering to a canvas-based rendering, some Chrome extensions may not function as intended on docs.google.com and may need to be updated. > If you are building your own integrations with Google Docs, we recommend using Google Work…
The part I don’t understand is how in the world is a renderer written in JavaScript better performing than their own Chrome c++ code? With Edge being a Chrome clone and Safari being also performant browser, what are they worried about?
Re: Google Docs will now use canvas based rendering
#13This might be a way to make Google Doc's feature that allows copy/paste to be disabled ( https://workspaceupdates.googleblog.com/2015/07/disable-down... ) to be more secure.
but it is false sense of security as any one can screenshot it and use ocr to generate text again?
Re: Google Docs will now use canvas based rendering
#14I would like to know which ui library they use.
I want to say that Flutter would be a good candidate, but I don't think it's ready for this. Or is it?
Re: Google Docs will now use canvas based rendering
#15RIP web accessibility when everyone starts doing this to make ad blocking more difficult
This is exactly the reason I don't use an ad blocker. In the long run, it will make everything worse, and I still probably won't be able to block ads. I'm clearly on the losing side of this though.
Re: Google Docs will now use canvas based rendering
#16If they're going to make the leap of switching the render layer, I'm surprised the leap isn't to flutter (which is supposedly stable/ready for production web apps?).
Flutter is Canvas-based on the web, so this post well-could mean a switch to Flutter. Hard to see how non-Flutter customer Canvas-renderer for Google Docs makes sense.
Re: Google Docs will now use canvas based rendering
#17Maybe because I am out of loop with web development, but this sounds like a huge change to me. So instead of HTML elements, there will be just one big element, and everything will be rendered there? How will text selection work for example? Will Google Docs basically implement a GUI library like GTK, which renders everything itself, but for the web?
I think they already have with Flutter
Re: Google Docs will now use canvas based rendering
#18I don't build extensions or work on much front end web lately but this reads like Google wants more control over their stuff. The web is becoming less open. > By moving away from HTML-based rendering to a canvas-based rendering, some Chrome extensions may not function as intended on docs.google.com and may need to be updated. > If you are building your own integrations with Google Docs, we recommend using Google Work…
The part I don’t understand is how in the world is a renderer written in JavaScript better performing than their own Chrome c++ code? With Edge being a Chrome clone and Safari being also performant browser, what are they worried about?
Their own renderer has to support all of HTML and CSS. Slapping some rectangles on a raster surface has a lot less to worry about.
Re: Google Docs will now use canvas based rendering
#19Re: Google Docs will now use canvas based rendering
#20I don't build extensions or work on much front end web lately but this reads like Google wants more control over their stuff. The web is becoming less open. > By moving away from HTML-based rendering to a canvas-based rendering, some Chrome extensions may not function as intended on docs.google.com and may need to be updated. > If you are building your own integrations with Google Docs, we recommend using Google Work…
The article says the reasons are, > to improve performance and improve consistency
[deleted]