← Back to context

Comment by ksec

3 months ago

Do we know Webkit, KHTML and Gecko's stand on this?

I know this is for security reason but why not update the XSLT implementation instead. And if feature that aren't used get dropped, they might as well do it all in one good. I am sure lots of HTML spec aren't even used.

6 comments

ksec

Reply
devmor  3 months ago

If it was just for security reasons, they could sponsor FOSS development on the implementation.

I am of the opinion that it is to remove one of the last ways to build web applications that don't have advertising and tracking injected into them.

  • xcrjm  3 months ago

    I get the impression they are ripping it out because they don't want to sponsor the FOSS volunteer working on it or deal w/ maintaining it themselves. The tracking/advertising take doesn't hold much water for me as adding those things to the page is something developers and companies choose to do. You could just as easily inject a tracking script tag or pixel or whatever via XSLT during transformation if you wanted.

  • umanwizard  3 months ago

    > I am of the opinion that it is to remove one of the last ways to build web applications that don't have advertising and tracking injected into them.

    Er, how so? What stops you from doing so in HTML/JS/CSS ?

Mr_Minderbinder  3 months ago

KHTML has been discontinued and was barely maintained for several years before. It has not been a relevant party for about a decade if not more.