Preview problem until i press "enter" on composer

[justoverclockl]

Bug Report

Current Behavior
Edit post preview doesn't work until i press "enter"

Steps to Reproduce
here video of this bug
https://streamable.com/zzr16l

Environment

• Flarum version: beta 16
• Website URL: http://flarum.it
• Hosting environment: [siteground shared]
• PHP version: 7.3
• Browser: [chrome]

Flarum core 0.1.0-beta.16
PHP version: 7.3.27
Loaded extensions: Core, date, libxml, openssl, pcre, sqlite3, zlib, bcmath, bz2, calendar, ctype, curl, dba, dom, enchant, hash, fileinfo, filter, ftp, gd, gettext, gmp, SPL, iconv, session, intl, json, mbstring, standard, mysqlnd, pcntl, mysqli, PDO, pdo_mysql, pdo_pgsql, pdo_sqlite, pgsql, Phar, posix, pspell, readline, Reflection, imap, shmop, SimpleXML, soap, sockets, sodium, exif, sysvmsg, sysvsem, tidy, tokenizer, wddx, xml, xmlreader, xmlrpc, xmlwriter, xsl, zip, memcached, ionCube Loader, Zend OPcache
+-----------------------------------+----------------+--------+
| Flarum Extensions                 |                |        |
+-----------------------------------+----------------+--------+
| ID                                | Version        | Commit |
+-----------------------------------+----------------+--------+
| flarum-markdown                   | v0.1.0-beta.16 |        |
| flarum-flags                      | v0.1.0-beta.16 |        |
| askvortsov-checklist              | v1.0.1         |        |
| flarum-pusher                     | v0.1.0-beta.16 |        |
| flarumite-simple-discussion-views | 0.3.0          |        |
| fof-best-answer                   | 0.4.0          |        |
| phenomlab-fancybox-wrapper        | 0.5            |        |
| fof-user-bio                      | 0.4.2          |        |
| fof-socialprofile                 | 0.3.0          |        |
| fof-polls                         | 0.3.2          |        |
| fof-share-social                  | 0.3.0          |        |
| sycho-github-milestone            | v0.1.1         |        |
| fof-analytics                     | 0.11.0         |        |
| fof-oauth                         | 0.2.1          |        |
| fof-formatting                    | 0.3.1          |        |
| flarum-tags                       | v0.1.0-beta.16 |        |
| flarum-suspend                    | v0.1.0-beta.16 |        |
| flarum-subscriptions              | v0.1.0-beta.16 |        |
| flarum-sticky                     | v0.1.0-beta.16 |        |
| flarum-statistics                 | v0.1.0-beta.16 |        |
| flarum-mentions                   | v0.1.0-beta.16 |        |
| flarum-lock                       | v0.1.0-beta.16 |        |
| flarum-likes                      | v0.1.0-beta.16 |        |
| flarum-lang-english               | v0.1.0-beta.16 |        |
| flarum-emoji                      | v0.1.0-beta.16 |        |
| flarum-bbcode                     | v0.1.0-beta.16 |        |
| flarum-approval                   | v0.1.0-beta.16 |        |
| fof-links                         | 0.6.0          |        |
| justoverclock-lang-ita-extended   | 1.0.5          |        |
+-----------------------------------+----------------+--------+
Base URL: https://flarum.it

[askvortsov1]

Looks like app.composer.fields.content() isn't updated when textarea is dynamically modified by the buttons.

[justoverclockl]

Looks like app.composer.fields.content() isn't updated when textarea is dynamically modified by the buttons.

this doen't happen if i use your extension "rich text"

[askvortsov1]

Looks like app.composer.fields.content() isn't updated when textarea is dynamically modified by the buttons.

this doen't happen if i use your extension "rich text"

Correct, because rich text doesn't use a textarea element, it's much more complex than that.

[justoverclockl]

https://i.ibb.co/vHh3y6F/U7s-Xxuep-AI.gif

[askvortsov1]

https://i.ibb.co/vHh3y6F/U7s-Xxuep-AI.gif

The error you linked is for my rich text extension, which isn't maintained by core; that should go in a separate discussion. That being said, your issue is that you're trying to set your text as "inline" code, where in this case, a code block would be more appropriate. Click the "+" button to see a dropdown with more options/