XStandard doesn't fall back to plain textarea
Christefano - December 4, 2007 - 06:15
| Project: | XStandard WYSIWYG Editor |
| Version: | 5.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | henrrrik |
| Status: | postponed |
Jump to:
Description
It's too bad that installing this module means that the fields configured in the XStandard module settings are actually uneditable unless the browser plugin is installed, too. it would be nice to be able to install this module and have XStandard be an option for the occasional user that has the browser plugin installed.
Also, with this module and the browser plugin installed there is no way to toggle it on or off. The ability to do this with TinyMCE (per role, per user and per form) makes installing TinyMCE a set it and forget it feature on some sites of mine. I'd like to do this with XStandard.
#1
XStandard can already be enabled per role and per textarea field. It would be nice if it was user-configurable on the profile page like TinyMCE is. I'll add that when I have the time.
I'm also looking into making it fall back to a normal input field if the plugin isn't installed. Patrick Lauke describes a method that should work nicely: http://www.splintered.co.uk/experiments/78/
#2
Thanks for posting the link. I'm new to XStandard and would love to support it when it has these requested features.
#3
The latest (dec 5th) 5.x snapshot falls back to a normal textarea field if the plugin isn't installed.
#4
I see that fallback support was added in commit #90321 (thanks!) but now I see the "If you can't see the XStandard WYSIWYG editor" error where the edit-body textarea should be when the XStandard browser plugin isn't installed.
I'm changing this to a bug report since the new feature doesn't seem to be working.
#5
It was removed. The fallback solution work at all in IE and at least one browser didn't post the
textareacontent to the server if it was wrapped in anobjecttag.#6
That explains it. :) Thanks for the response.
It's too bad that
get_browser()or Browscap aren't able to detect installed plugins. Would you be able to use a detection script? XStandard has one at http://xstandard.com/en/documentation/xstandard-dev-guide/web-integratio...#7
The plugin can be detected via JavaScript, but I doubt that it's possible to load the plugin by inserting the
objectwith JS. I'll give it a try when I have some spare time though.#8
#9