-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spaces are overwritten in DualView mode #93
Comments
Here's the problem in a nutshell: In an attempt to avoid extraneous spaces at the end of a block element ( The bug doesn't occur with inline elements ( 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:
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. |
Hello, that cannot be the case under any circumstances. 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 |
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
The text was updated successfully, but these errors were encountered: