Discussion: MIME-typing the Document / Document Fragment?
See original GitHub issueFiled under Bigger Fish To Fry But:
Working on the copy-paste issues, it occurred to me that in a world dominated by Slate-based rich text editors, it would pose a problem to copy and paste between editors with incompatible schemas.
To that end, I’m opening a discussion on whether a Slate Editor should mark its identity in some way (as sort of MIME type), and that information can be serialized in data-slate-fragment
.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:5 (3 by maintainers)
Top Results From Across the Web
DocumentFragment - Web APIs | MDN
Chrome Edge
DocumentFragment Full support. Chrome1. Toggle history Full support. Edge...
DocumentFragment() constructor Full support. Chrome29. Toggle history Full support. Edge...
append Full support. Chrome54. Toggle...
Read more >Add a general fragment identifier handler #5599 - GitHub
The fragment of text/csv documents works as a selector for columns, rows, cells using row , col and cell keywords. At moment jupyterlab...
Read more >Document Fragments and why you should use them
A document fragment is a fragment of a Document Object Model (DOM) tree, a chunk of tree that's separated from the rest of...
Read more >Migrate apps from Internet Explorer to Mozilla - Archive of obsolete ...
First, I'll discuss the differences in the way HTML behaves between Mozilla and Internet Explorer. ... Mozilla creates document fragments through document.
Read more >RFC 2046: Multipurpose Internet Mail Extensions (MIME) Part ...
These issues are discussed later in this document. The two composite top-level media types are: (1) multipart -- data consisting of multiple entities...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This was something I had planned to take on after https://github.com/ianstormtaylor/slate/pull/2933, but then 0.50 landed. Since our main implementation is still pre-refactor, upstreaming work hasn’t been a priority.
I haven’t looked into the current state of copy / paste post-refactor, but I don’t think this would be hard to layer on.
@justinweiss sounds awesome.
When we move these, let’s rename them to
getDOMEventTransfer
I think, for clarity and symmetry with the other DOM helpers.