Klik om te bewerken

[denvergeeks]

@pipkin

I implemented this behavior, so that later on I could extend the plugin to allow reliable insertion/editing of fragments from the topic view page, equivalent to the edit-button shown below (but a bit more robust):

@pfaffman

This seems like something that would have wide appeal. It can be hard to find your place in a long post.

I could not agree more

Last year I submitted a similar feature request…

Fast Edit - Please Show Selected Portion as Selected Whenever the Composer Opens

When I select a portion of text to “Fast Edit”, and then the Composer opens, I expect that the text I have selected will already be selected in the Composer. At this point, the cursor often does not even appear anywhere near my selected text, and often even arrives in the Title. It is cumbersome and confusing to have to visually locate the resulting position of the cursor, and also to have to then use the mouse to re-position the cursor and re-select the portion I already had selected for edit…

[lubezniy (Victor Lyubezny)]

Hi.

After a latest Discourse update (Discourse v3.5.0.beta8-dev — Commits · discourse/discourse · GitHub — Ember v5.12.0), Reply button stopped to work. This problem was solved when Click To Edit plug-in was turned off in the admin interface. Developer console showed JavaScript addEventListener error in ember.js file (object named “textarea“, i can’t copy exact text now).

[cmdntd]

It has serious error in the latest version of discourse editor (both mardown and rich-text one)

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading ‘type’)

It has error in the latest version of discourse editor · Issue #1 · thijsbrilleman/discourse-click-to-edit · GitHub

[Monikas (JustMonika)]

Na het updaten van Discourse en het ingeschakeld houden van deze component:

• De werkbalk van de editor reageert helemaal niet meer

• De knoppen “Verzenden” en “Sluiten” werken niet

• De enige manier om de editor te verlaten is door de pagina te vernieuwen

[TheBaby5 (Bug Reporter)]

@Monikas heeft gelijk!
Het werkbalk van de editor wordt volledig onresponsief en er zijn nog veel meer problemen na het updaten van Discourse!

[pipkin (Thijs)]

Bedankt voor je melding, we zijn ermee bezig. Ik laat het je weten.

[pipkin (Thijs)]

The issue has been solved in Bug fix: Updated plugin to reflect new delayed loading of markdown ed… · thijsbrilleman/discourse-click-to-edit@1d65a03 · GitHub .

The plugin can be re-enabled.

@david The broken tag can be removed.

[cmdntd]

Het is nu oké, maar…

Het lijkt nogal traag om te bewerken. Ik denk dat js het moeilijker maakt om opnieuw te laden in deze nieuwe editor?

Wanneer ik navigeer, is dit nog steeds oké. Maar het lijkt vast te lopen als ik tekst op de cursor bewerk.

Dus ik denk dat het beter is als ik tekst kan bewerken zonder js opnieuw te laden op de cursor.