They are also including the “CSSOM” and “rendering tree” as part of what they consider subject to “unlawful reproduction and modification”.
So, according to them, the rendering tree is also part of their IP… which is bonkers, since it’s the browser the one who implements this and even different browsers (or different versions of the same browser) might actually have different rendering strategies, different trees… different CSS extensions (or omisions/deprecations), etc. You basically would be potentially violating their IP if you used any browser different than what they specifically might have had in mind (which we don’t even have a way to know for sure unless they clearly state it…).
It’s like a painter suing someone for using glasses and altering the lightwaves coming from their painting…
They are also including the “CSSOM” and “rendering tree” as part of what they consider subject to “unlawful reproduction and modification”.
So, according to them, the rendering tree is also part of their IP… which is bonkers, since it’s the browser the one who implements this and even different browsers (or different versions of the same browser) might actually have different rendering strategies, different trees… different CSS extensions (or omisions/deprecations), etc. You basically would be potentially violating their IP if you used any browser different than what they specifically might have had in mind (which we don’t even have a way to know for sure unless they clearly state it…).
It’s like a painter suing someone for using glasses and altering the lightwaves coming from their painting…
also if you update the browser and the update uses new rendering code that does things differently, that would also result in a copyright violation.
simply, these things are intermediate “products” of the web browser, not of the web developer.