steveathon / bootstrap-wysiwyg

Tiny bootstrap-compatible WYSIWYG rich text editor
MIT License
661 stars 1.71k forks source link

dropdown button (font size \ family) #92

Open amjazzed opened 8 years ago

amjazzed commented 8 years ago

selecting a text then holding a click on the 'font size' button without releasing, then slightly move the cursor a little inside the clicked button will remove selection , but selecting a font size value after the drop down appears will restore the selection and change size of selected text. THIS WHEN WE DO IT SLOWLY.

but doing it FAST will cause it to sometimes work and sometimes not .

is there a solution ?

codewithtyler commented 8 years ago

At this time no. You're the first person to report this issue.

From a quick glance at the HTML the issue itself may just be in how we've got the Bootstrap dropdown setup. I'm not sure that our HTML is up to date with the latest version of Bootstrap. I'll take some time later today to look at it and compare it the latest Bootstrap docs.

codewithtyler commented 8 years ago

The only thing that's inconsistent with the Bootstrap docs is we're missing role="button" aria-haspopup="true" from the anchor tag of the dropdown. We also have a <b></b> tag instead of a <span></span> tag for the caret icon.

I was able to replicate your issue that first time. Since then I've been unable to replicate the results. It doesn't seem to happen consistently.

Note: Sorry, I originally posted this comment under the wrong issue.

spreadred commented 7 years ago

I was able to replicate the issue a few times, but I could not reliably get it to occur.

I did notice that after you select text in the editor and then click and hold the text size button, and moving the mouse left or right results in the selection highlight changing to reflect cursor position. This change in highlighting doesn't seem to matter though, as when I release the font size button and pick a size, it applies that formatting to the original, intended selection.

steveathon commented 6 years ago

Weird bug. It could have been in the way the events were firing in the browser. Has anyone been able to replicate it in the latest builds?