CSS Paint API: New possibilities in Chrome 65

#1

Post by syrusakbary » Fri, Jan 19, 2018, 10:56 PM UTC

CSS Paint API: New possibilities in Chrome 65
developers.google.com

Re: CSS Paint API: New possibilities in Chrome 65

#2

Post by freddywang » Sat, Jan 20, 2018, 12:00 AM UTC

we already had this all the way back in 2008. It's called webkit css canvas! Iconapp.io is using that heavily!

background: -webkit-canvas(mycanvas);

Re: CSS Paint API: New possibilities in Chrome 65

#3

Post by matmo » Sat, Jan 20, 2018, 12:05 AM UTC

I always find it interesting that Chrome is charging ahead full steam on experimental API's like this while most other browsers have given no intent to implement them yet.

Did Chrome come up with Houdini? Are they being brave or pushy here?

Re: CSS Paint API: New possibilities in Chrome 65

#4

Post by foob » Sat, Jan 20, 2018, 12:10 AM UTC

matmo wrote: post #3

I always find it interesting that Chrome is charging ahead full steam on experimental API's like this while most other browsers have given no intent to implement them yet. Did Chrome come up with Houdini? Are they being brave or pushy here?

It's a joint W3C Technical Architecture Group and CSS Working Group initiative, you can find a lot of details in this post from the Opera developer blog [1].

[1] https://dev.opera.com/articles/houdini/

Re: CSS Paint API: New possibilities in Chrome 65

#5

Post by tzahola » Sat, Jan 20, 2018, 12:17 AM UTC

Another day, another wart on the modern web stack.

Re: CSS Paint API: New possibilities in Chrome 65

#6

Post by andybak » Sat, Jan 20, 2018, 12:25 AM UTC

tzahola wrote: post #5

Another day, another wart on the modern web stack.

Distinguish wart from feature

Re: CSS Paint API: New possibilities in Chrome 65

#7

Post by zawerf » Sat, Jan 20, 2018, 12:32 AM UTC

You've always been able to use a canvas normally and then create a url to it using toDataUrl. Alternatively toBlob then createObjectURL which I think might be more performant than data url which requires encoding/decoding base64.

So I guess the main thing added is convenience? Am I missing something here? Adding CSS that requires corresponding JS code is also new territory isn't it (I can't think of anything else that does this)?

Re: CSS Paint API: New possibilities in Chrome 65

#8

Post by mintplant » Sat, Jan 20, 2018, 12:33 AM UTC

matmo wrote: post #3

I always find it interesting that Chrome is charging ahead full steam on experimental API's like this while most other browsers have given no intent to implement them yet. Did Chrome come up with Houdini? Are they being brave or pushy here?

> Did Chrome come up with Houdini?

Most certainly not. I know people at Mozilla who've been working on Houdini-related features for a while now (cf. https://wiki.mozilla.org/CSS/Houdini). Chrome is just the first to release here.