You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Chrome (haven't confirmed Firefox) open the Yahoo mail editor.
Type some text.
Click the B (bold) button.
Click back into the compose area.
Right-click and click "Markdown Toggle".
Markdown Here's "The selected field is not valid for Markdown rendering. Please use a rich editor." will result.
The problem is that findFocusedElem() is finding the bold button instead of the compose box.
Not sure yet how to fix it. activeElement isn't an array, it's a single value, so it's not like there's a concept of more than one active element... even though the compose box clearly has focus. Maybe activeElement isn't the correct thing to use for finding the focused element?
Does each iframe have its own activeElement (that can all be meaningful at the same time)? Maybe all iframes should be traversed until a valid Markdown Here target is found?
Workaround: Click on the font size combo box and then back into the compose box. (Which makes no sense, but it works.)
This bug is especially bad since the "maintain pre-formatted text" feature was added, which encourages (or at least doesn't dissuade users) to click the formatting buttons.
The text was updated successfully, but these errors were encountered:
There is a similar problem with Hotmail, except worse. If you tab from the Subject field to the email body, the activeElement gets stuck on the button for "bold". This seems to only happen in Chrome, and not Firefox.
On the upside, the new Yahoo interface may have fixed itself. I'm not sure yet, though.
Workaround: Click into the message body. If you tab into it, click out of it and then back in.
I have absolutely no idea how to fix this. I'm going to create a test page and ask on StackOverflow...
Reproduction:
Markdown Here's "The selected field is not valid for Markdown rendering. Please use a rich editor." will result.
The problem is that
findFocusedElem()
is finding the bold button instead of the compose box.Not sure yet how to fix it.
activeElement
isn't an array, it's a single value, so it's not like there's a concept of more than one active element... even though the compose box clearly has focus. MaybeactiveElement
isn't the correct thing to use for finding the focused element?Does each
iframe
have its ownactiveElement
(that can all be meaningful at the same time)? Maybe alliframes
should be traversed until a valid Markdown Here target is found?Workaround: Click on the font size combo box and then back into the compose box. (Which makes no sense, but it works.)
This bug is especially bad since the "maintain pre-formatted text" feature was added, which encourages (or at least doesn't dissuade users) to click the formatting buttons.The text was updated successfully, but these errors were encountered: