-
-
Notifications
You must be signed in to change notification settings - Fork 828
Change Rich Quoting HTML Format over the wire #1701
Conversation
the quote target is sent in the cite attribute of the blockquote to make parsing easier, it is also provided as a link within the body for clients that do not yet understand rich quoting Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
TravisCI Chrome is still broken |
I think we'll have to do the due diligence here as this is basically spec stuff (even if the actual Shall we get some suggestions on a google doc and try to get some feedback? |
So I'm all for instead throwing |
True, but in the context of a forum post, only being able to cite one message and in no particular point in your message feels quite limiting. I guess this is essentially the same argument as Pills where we eventually put everything into the HTML, so perhaps it's better to be consistent, although I still have the same concern there. Anyway, arguing myself back & forth aside, unassigning myself to let others chime in. |
Because of element-hq/element-web#5967 (comment) the semantics are entirely different IMO. |
8ec9abb
to
36267f6
Compare
The above would also fix (and seems to be the sanest/only sane way to fix) things like: element-hq/element-web#6061 |
Could also fix node replacing nastiness/race conditions such as element-hq/element-web#6059 (comment) |
Replaced by #1741 |
To something a little richer that will look better on clients that do not yet support this feature whilst still keeping it as easy to parse
Fixes element-hq/element-web#5967
Fixes element-hq/element-web#5982