therealglazou / bluegriffon

BlueGriffon, the Web editor
Mozilla Public License 2.0
294 stars 71 forks source link

Spaces are overwritten in DualView mode #93

Open schabau opened 3 years ago

schabau commented 3 years ago

I like to use BlueGriffon 3.1 in DualView mode, but discovered a bug.

When the DualView mode is activated and you write on the WYSIWYG page, spaces are often overwritten.

You write a word, make a space and when you enter the first letter of the next word, the cursor jumps back to the end of the previous word and overwrites the space. Sometimes you manage to write a few words, but then it happens again. The text looks like this, for example: "Todayisabeautiful day, onlyBlueGriffonannoys mealittle."

This only happens in DualView mode when writing on the WYSIWYG page. I am using the current version BlueGriffon 3.1 under Windows 10 x64.

Can this problem be solved?

Many greetings Schabau

pbarney commented 3 years ago

Here's the problem in a nutshell:

In an attempt to avoid extraneous spaces at the end of a block element (<p>, <div>, etc.), the program will remove them after a period of time where no keyboard input has occurred. Unfortunately, that time appears to be one second or less.

The bug doesn't occur with inline elements (<span>, <textarea>, <time>, etc.) as they replace the ending space with a &nbsp; entity. If you begin typing again, the &nbsp; is replaced with an actual space. I believe this is how block elements should work as well, so this may be an easy fix; I honestly don't know.

There seems to be a timer involved. If you keep typing at a rapid pace, the problem doesn't happen. If you stop to think for more than two seconds, it switches to "remove empty spaces at the end of a block element" mode, erasing all of your spaces.

Possible workarounds:

  1. Type really fast and don't stop.
  2. If you have to stop, get in the habit of pressing the spacebar before you start typing your next word.
  3. Wrap all of your text inside <span> tags.
  4. Type in another editor and paste into BlueGriffon.

Obviously, these workarounds all suck. Definitely a bug here, but apparently, this space was abandoned long ago by @therealglazou, which is too bad because I think a lot of people still want a standards-compliant editor that can write semantically valid HTML.

schabau commented 3 years ago

Possible workarounds:

  1. Type really fast and don't stop.

Hello,

that cannot be the case under any circumstances. The problem occurs when writing is pouring away and not during any breaks. And only in dual view mode.

But I've come to terms with the fact that nothing more will happen at BlueGriffon anyway. BluGriffon now appears to be dead too.

Best wishes