Remove write and add more details on read.

[snianu]

Closes #????

The following tasks have been completed:

• [ ] Confirmed there are no ReSpec/BikeShed errors or warnings.
• [ ] Modified Web platform tests (link to pull request)

Implementation commitment:

• [ ] WebKit (https://bugs.webkit.org/show_bug.cgi?id=)
• [ ] Chromium (https://bugs.chromium.org/p/chromium/issues/detail?id=)
• [ ] Gecko (https://bugzilla.mozilla.org/show_bug.cgi?id=)

[snianu]

@sanketj Addressed all comments. PTAL. For write I can create a new explainer to describe the changes we're making in the sanitization and mention it in the read explainer as a link. wdyt?

[sanketj]

@sanketj Addressed all comments. PTAL. For write I can create a new explainer to describe the changes we're making in the sanitization and mention it in the read explainer as a link. wdyt?

Thinking about this some more, I don't think we can specify that write should provide unsanitized HTML as Safari has different behavior. Perhaps it is sufficient to mention in this explainer that the unsanitized option in read also allows browsers that write unsanitized HTML to roundtrip HTML content better?

[snianu]

@sanketj Addressed all comments. PTAL. For write I can create a new explainer to describe the changes we're making in the sanitization and mention it in the read explainer as a link. wdyt?

Thinking about this some more, I don't think we can specify that write should provide unsanitized HTML as Safari has different behavior. Perhaps it is sufficient to mention in this explainer that the unsanitized option in read also allows browsers that write unsanitized HTML to roundtrip HTML content better?

Added this in the intro section. Thanks!

[snianu]

@sanketj Addressed all comments. PTAL, thanks!