This page provides an area for testing the current functionality of
SpellBound and is a live example of how to integrate SpellBound in a
web page alongside ieSpell.
If you are using a browser based on Mozilla you will see a SpellBound
Status box in the upper right corner. This box provides information for
the current state of SpellBound (e.g. does it need to be installed or
upgraded, is a spell check active, was the last spell check canceled,
etc.) to demonstrate what information can be provided programmatically
when integrating SpellBound into a site.
For information on how to launch a spell check please
refer to the How do I use it? section on the
FAQ page.
INPUT and TEXTAREA elements that have a readonly, disabled, or ieSpell_ignored attribute are not spell checked.
Other elements that should not be spell checked such as password input elements are not spell checked.
INPUT and TEXTAREA elements are spell checked and you may also select the text prior to spell checking in either of these elements to spell check just the selected text. Spell checking of just the selected text in any other elements is not supported. Also, when SpellBound is launched from a web page element (e.g. button, etc.) checking just the selected text is not supported. If you would like to provide selection text checking from a web page element you can reselect the text prior to launching SpellBound in your JavaScript event handler for launching SpellBound.
An element can be added to a web page to launch a spell check on a specific element or the entire web page.
Checks the spelling of only the textarea above this button.
Checks the spelling of all elements that can be spell checked on this web page.
Documents with designMode="on" (e.g. the following two editable IFRAME elements) are spell checked.
Checks the spelling of the iframe that has designMode="on" above.
INPUT and TEXTAREA elements that have a readonly, disabled, or ieSpell_ignored attribute are not spell checked.
Other elements that should not be spell checked such as password input elements are not spell checked.
INPUT and TEXTAREA elements are spell checked and you may also select the text prior to spell checking in either of these elements to spell check just the selected text. Spell checking of just the selected text in any other elements is not supported. Also, when SpellBound is launched from a web page element (e.g. button, etc.) checking just the selected text is not supported. If you would like to provide selection text checking from a web page element you can reselect the text prior to launching SpellBound in your JavaScript event handler for launching SpellBound.
An element can be added to a web page to launch a spell check on a specific element or the entire web page.
Checks the spelling of only the textarea above this button.
Checks the spelling of all elements that can be spell checked on this web page.
Documents with designMode="on" (e.g. the following two editable IFRAME elements) are spell checked.
Checks the spelling of the iframe that has designMode="on" above.
Notes
- I have chosen not to add support for contentEditable at this time due to not receiving requests for contentEditable support along with the additional overhead created by supporting it. If you have a web page where you would like to spell check contentEditable elements please let me know by using the Contact form.
- I have not added scripts or controls for editing the rich text elements (e.g. designMode) in order to reduce the size of the page.
- After viewing an IFRAME with designMode="on" redirects may stop functioning due to Bug ID 233830
- SpellBound reports a spell check as canceled if the user closes the spell check before correcting or ignoring all possible misspelled words in all elements that are to be spell checked. This is intended behavior since the spell check was canceled even though some of the words were checked.
- To spell check an IFRAME in designMode you must first wait until the entire page including the IFRAMEs has finished loading. The same is true to edit the IFRAME so even though it may appear to be a bug I don't consider it a SpellBound problem. This is mainly to forewarn you and to lessen reports of this being a bug since this is a requirement of designMode and outside of my control.
- When using ieSpell_ignored with XHTML the attribute name is case sensitive. I believe this is will also true when using ieSpell but it will depend on whether IE will properly support XHTML etc.
- I have been unable to get designMode to work with an IFRAME that is served as application/xhtml+xml and though I haven't researched this I suspect this is by design.
- When viewing the page with Internet Explorer several elements have been reduced in size due to the way it will improperly render width 100% for several of the elements.
Copyright © 2004-2005 Robert Strong All rights reserved
Valid XHTML 1.0 Transitional served as text/html - Page Last Updated: Apr. 17, 2005
Valid XHTML 1.0 Transitional served as text/html - Page Last Updated: Apr. 17, 2005