James Bradford

I’ve open up a feature request here. Could you maybe go to that thread and clarify repo steps?

should be fixed in v2.0

open up an issue here if you have any more problems

Thanks!

fixed now in v2.0

This should work in v2.0 which was just released. let me know how it goes. Please open up an issue here if it does not work.

Thanks

v2.0 is released now. This should be fixed.

Thanks!

Could you please explain further?

What is the plugin not doing that you would expect it to? How would it integrate with the Google Libraries Plugin?

Sorry for the late response.

This might be fixed in Version 2.0 that will be released late May.

Until then, You can download the .zip of the Version 2.0 release and install it yourself.

Hope this helps.

Version 2.0 is available now if you want to install it yourself. It should resolve this issue.

It should be pushed out publicly at the end of May.

Its not broken, but it is supposed to be this way. Code is never spellchecked. Much of the code would come up as misspelled, because it isn’t English.

There is something like a spellchecker, but it checks for errors in the HTML/Shortcode syntax.

Sorry I can’t help with that.

P.S. I like your sepllchcek tag on the thread

This will be fixed in Version 2.0 that will be released late May.

Until then, You can download the .zip of the Version 2.0 release and install it yourself.

Hope this helps.

The Editor getting focus too early is a bug I’ll fix later.

As for the find feature…

The browser’s find functionality only works with the syntax-highlighter if you can already see the text onscreen(defeats the purpose of ‘find’, I know).

It will be fixed eventually.

Until then, I’ve posted a workaround here.

So…

Yes, The browser’s find functionality only works with the syntax-highlighter if you can already see the text onscreen(defeats the purpose of ‘find’, I know).

It will be fixed eventually.

Until then, I’ve posted a workaround here.

I cannot do this. It would require having to rewrite every color theme to support the difference.

Sorry

to clarify:

This is an issue with buttons not showing up in the editor bar, correct?

Thanks for the heads up. I’ve already fixed this in v2.0 which will be out soon.