Jeremy Ruston

It would be nice if the core could use the new API if available, falling back to the previous implementation if not.

Hi @Leilei332 @pmario > Migrating to native clipboard api shares a the same problem with migrating to native crypto api: Native clipboard api is asynchronous, while the old implementation that...

> @Jermolene I had that thought as well and went with the event associated name for now as that is what the testing has focused on. Perhaps `copyObjectProperties`? Or `copyObjectPropertiesSafe`...

Hi @well-noted apologies for the delay. I think this is a good approach and would be happy to merge this. I think we will also need a wafer thin implementation...

Thanks @pmario @ericshulman

Thanks @CrossEye @yaisog @pmario I would like to see something along these lines in the core. I have always liked Alberto Molina's "TiddlyWiki for Scholars" at http://tw5.scholars.tiddlyspot.com/ which features bottom...

Thanks @linonetwo. I am still very keen to be able to offer a WYSIWYG editor. If it's not ready for v5.4.0 then it would make an excellent tentpole feature for...

Hi @pmario I think it might be easier to review this PR if we could remove the whitespace updates, and just include the changes necessary to get dprint installed and...

Thanks @pmario it would make the commit history very confusing. Why can't we merge the dprint integration in one PR and then immediately after merge the changes that it makes...

Thank you @pmario, I think this is good to go.