I recently updated to the latest version of Google Chrome (32.0.1700.76)
and have since noticed difficulties using the available HyperLink tool within the editor in the forums. Basically, I have been able to reproduce it locally through the following steps :
Type some text that you would like to add as a link.
Highlight the text that you want to "wrap" with the link.
Click the Hyperlink icon within the Editor :
After typing in your appropriate link, it seems that the Insert option doesn't seem to respond at all and will not submit the available form in the new Window :
I've had to resort to manually editing the elements using the HTML option as an easier approach during this time, I just wanted to see if anyone else was aware of the issue or experiencing the issue (although it is more
a TinyMCE issue than one with our forums).
Of course shortly after posting the issue, it seems that there are two ways around this :
When an element on the popup form has focus, simply hit the "Enter" key to submit it as you would with most forms.
It seems that selecting the actual "Insert" option is a bit tricky and you have to explicitly select the border of the button (you'll notice the cursor will change when you are able to click it).
All-Star
113010 Points
18360 Posts
MVP
Issue Saving Links (Possibly related to Chrome Update)
Jan 16, 2014 02:20 PM|Rion Williams|LINK
I recently updated to the latest version of Google Chrome (32.0.1700.76) and have since noticed difficulties using the available HyperLink tool within the editor in the forums. Basically, I have been able to reproduce it locally through the following steps :
I've had to resort to manually editing the elements using the HTML option as an easier approach during this time, I just wanted to see if anyone else was aware of the issue or experiencing the issue (although it is more a TinyMCE issue than one with our forums).
All-Star
113010 Points
18360 Posts
MVP
Re: Issue Saving Links (Possibly related to Chrome Update)
Jan 16, 2014 02:22 PM|Rion Williams|LINK
Of course shortly after posting the issue, it seems that there are two ways around this :