NodeBB (or site) composer button incompatibility.
-
IIRC this works properly with Chrome and other browsers, but in Edge if you highlight text and hit the eraser or title buttons, it inserts the text AFTER your highlighted stuff instead of wrapping it. So you'll wind up with something like
blah<abbr title=""></abbr>(assuming blah was highlighted).
-
@FrostCat Also. See what happened in quoted text up there? That right there is deranged, @ben_lubar @julianlam, given that it's the exact opposite of what happens with normal text!
-
The eraser and abbr buttons are provided by a plugin written by @NedFodder.
GitHub - NedFodder/nodebb-plugin-tdwtf-buttons: Composer Buttons for WTDWTF
Composer Buttons for WTDWTF. Contribute to NedFodder/nodebb-plugin-tdwtf-buttons development by creating an account on GitHub.
-
@FrostCat said in NodeBB (or site) composer button incompatibility.:
Also. See what happened in quoted text up there? That right there is deranged, @ben_lubar @julianlam, given that it's the exact opposite of what happens with normal text!
The
`block is a code block. It's supposed to render its contents as plain text, exactly the opposite of normal text which is markdown'd.
-
@boomzilla The problem happens with the stock composer buttons too:
In fact, Edge just seems to insert the formatting wherever the cursor started when highlighting. In my case, I double-clicked in
happensand highlighted extra text, I'm guessing @FrostCat started at the end of a word and highlighted back using arrow keys.
-
@ChaosTheEternal Oh, good, then @FrostCat can open a bug report with Mi¢ro$oft.
-
@anotherusername Bah. Doing it not the way I expected it is
.
-
@boomzilla It'd probably get fixed
fasterthat way!
-
@FrostCat It's not really cool to report bugs to websites when the problem is in your alpha release browser.
-
@boomzilla said in NodeBB (or site) composer button incompatibility.:
@FrostCat It's not really cool to report bugs to websites when the problem is in your alpha release browser.
[joke about an alpha browser is appropriate for alpha forum software goes here]
-
@boomzilla said in NodeBB (or site) composer button incompatibility.:
@ChaosTheEternal Oh, good, then @FrostCat can open a bug report with Mi¢ro$oft.
I reproduced the issues on IE11. Chrome and FF seem to be fine.
While the issue @FrostCat reported is probably with the composer and not my plugin, I did just find an issue with the plugin. When you double-click to select a word on Windows, the OS will helpfully™ also select the space character after the word. Thanks to @ben_lubar, the trailing space is removed before the composer adds the formatting to the selection. However, my plugin doesn't know that the space has been removed. When it tries to move the cursor, it will move it to the wrong spot.
-
@boomzilla said in NodeBB (or site) composer button incompatibility.:
@FrostCat It's not really cool to report bugs to websites when the problem is in your alpha release browser.
what about reporting bugs affecting A browser version that was EOL'd in August 2013?
-
It definitely
d<abbr title=""></abbr>oesnot also work in IE11 on Windows 10.This is what happens in IE11 when I use the arrows to highlight the word "does" and make sure not to have the space afterwards highlighted. Now sure why the insertion point was after the d and not before it.
-
@accalia Using Firefox is its own punishment. Using such an old version is just the shit gravy on the guano cake.
-
@accalia said in NodeBB (or site) composer button incompatibility.:
@boomzilla said in NodeBB (or site) composer button incompatibility.:
@FrostCat It's not really cool to report bugs to websites when the problem is in your alpha release browser.
what about reporting bugs affecting A browser version that was EOL'd in August 2013?
Does the same bug happen in a newer browser?
If so then
-
@FrostCat said in NodeBB (or site) composer button incompatibility.:
@accalia Using Firefox is its own punishment. Using such an old version is just the shit gravy on the guano cake.
not going to disagree.
the mascot for the browser is cute, and it used to be a good browser...... but today? today just use Chrome and install a skin to make it look like firefox if you have to.....
-
@accalia said in NodeBB (or site) composer button incompatibility.:
@FrostCat said in NodeBB (or site) composer button incompatibility.:
@accalia Using Firefox is its own punishment. Using such an old version is just the shit gravy on the guano cake.
not going to disagree.
the mascot for the browser is cute, and it used to be a good browser...... but today? today just use Chrome and install a skin to make it look like firefox if you have to.....
Good. You're starting to learn.
-
@Lorne-Kates said in NodeBB (or site) composer button incompatibility.:
Does the same bug happen in a newer browser?
i don't know. i've switched to using a real browser that actually fixes bugs in a reasonably timely fashion.
-
@accalia said in NodeBB (or site) composer button incompatibility.:
just use Chrome
Chrome does a few things weirdly, like the way it highlights text when you have multiple indented blocks. IE/Edge will only highlight the text; Chrome highlights the whole area. That seems wrong somehow.
-
@Lorne-Kates said in NodeBB (or site) composer button incompatibility.:
@accalia said in NodeBB (or site) composer button incompatibility.:
@FrostCat said in NodeBB (or site) composer button incompatibility.:
@accalia Using Firefox is its own punishment. Using such an old version is just the shit gravy on the guano cake.
not going to disagree.
the mascot for the browser is cute, and it used to be a good browser...... but today? today just use Chrome and install a skin to make it look like firefox if you have to.....
Good. You're starting to learn.
doesn't change the fact that that version is almost three years past EOL. your version may have been good when it was released, but today it's out of date and insecure (thanks to the lack of security patches) crap.
-
Repro'd at meta.nodebb. I'll submit a bug report if no one beats me to it...
