You are not logged in.
Using the range object in Mozilla you are able to find out the nodes where the selection starts and ends, see http://developer.mozilla.org/en/docs/DOM:range. Unfortunately the range object in IE as well as the documentation on msdn are dreadfully insufficient, see http://msdn.microsoft.com/workshop/auth … trange.asp. In short it is hard to impossible to work with nodes with IE textRange object, as the moving methods work with categories like character and sentence.
In fact the documentation is a joke. What is one supposed to do with vague statements like "Modify the extent of the text range by moving its start and end positions with methods such as move, moveToElementText, and findText." instead of a comprehensive list of the methods available???
As this obviously does not seem to be a known bug, I'd ask you to look at this topic http://xinha.gogo.co.nz/punbb/viewtopic.php?id=899, otherwise I see no means how we could at all find out what your problem may be. Especially, do you have any javascript errors?
Additionally I have to mention that this is not a drupal support forum
Kind regards
ray
That should absolutely not happen, as there is nothing much more happening than resizing the editor when going into fullscreen. I can't explain that ![]()
Please create a ticket if you find any bugs
Yes, you are right. htmlarea.js is only still included to make the transition softer and don't break existing installations
I'm afraid that won't work either, I suppose
This could be related to this: Same Origin Policy
yeah, I was somehow stuck ![]()
hmm...actually I think it still does work (tried it out with an example from rev 2)
If the line
require_once(realpath(dirname(__FILE__) . '/../../contrib/php-xinha.php'));is in plugins/ImageManager/config.inc.php it seems the file is found otherwise you would get an error message saying something like
Fatal error: main(): Failed opening required '' (include_path='.;c:\apachefriends\xampp\xampp\php\pear\') in C:\apachefriends\xampp\xampp\htdocs\xinha\plugins\ImageManager\config.inc.php on line 286but if xinha_read_passed_data() nevertheless is undefined this can only mean that you have to update contrib/php-xinha.php
I have commited a new version that contains a readme file. I hope this clears your questions ![]()
How would this relate to Xinha?
yes this seems to be impossible
http://xinha.gogo.co.nz/punbb/viewtopic.php?id=790
EDIT:
Sorry, this would be: no this does not seem to be impossible. Don't know why I got this wrong
...include an URL to your page, so that other users can have a look at your HTML/JavaScript and help you spot the error.
Also include:
* the browser used
* the Xinha revision you are using (click on the [i] icon in the toolbar, look at the version tab)
* any JavaScript error messages that may occur
If you have searched the forum and the tickets for the issue and haven't found anything, it seems you are the first one to experience this.
In that case it is unlikely that anybody can help you, if you do not provide enough information!
To my knowledge Xinha does and always has used <strong> for bold text in either browser.
Is it IE 6 or 7?
It would be easier to find a solution if we could have a look at the resulting HTML, as the php part is of no importance, except for this part:
<textarea name="content" id="content" cols="50" rows="15"> <?php echo htmlspecialchars(stripslashes($content));?> </textarea>Entities are generally not used inside the editor, both browsers, except &, ", <, >
This is OK if you use UTF-8 encoding in your page, or you surely only use characters that are available in your charset.
The HtmlEntities plugin cares for the conversion of "special characters" to entities which is
Technically it works very simple: It takes a long list of characters and their respective entity and fills the config.specialReplacements variable with them.
This list of entities used can be found and edited in the plugin directory. If you choose to edit the list, you can (should) save it under a new name and reference this by using
xinha_config.HtmlEntities.EntitiesFile = "/path/to/your/file.js"Then you can update Xinha without overwriting your changes
yeah, thats right
simply pull xinha_editors out of your config
Page:
<script type="text/javascript">
xinha_editors =
[
'myTextArea'
];
</script>
<script type="text/javascript" src="../htmlarea.js"></script>
<script type="text/javascript" src="config.js"></script>config.js:
//xinha_editors = null; <-------------------------------- Don't forget this!
xinha_init = null;
xinha_config = null;
xinha_plugins = null;
// This contains the names of textareas we will make into Xinha editors
xinha_init = xinha_init ? xinha_init : function()
{
/** STEP 1 ***************************************************************
* First, what are the plugins you will be using in the editors on this
* page. List all the plugins you will need, even if not all the editors
* will use all the plugins.
************************************************************************/One simple question: Do you have each textarea in your HTML?
Sorry, I couldn't reproduce what you describe. (Sorry for copy/paste)
Which browser?
Any JS errors?
Sorry, I couldn't reproduce what you describe
Sorry, I couldn't reproduce what you describe
/**
* Size the editor to a specific size, or just refresh the size (when window resizes for example)
* @param width optional width (CSS specification)
* @param height optional height (CSS specification)
* @param includingBars optional boolean to indicate if the size should include or exclude tool & status bars
*/
xinha_editors.myTextArea.sizeEditor = function(width, height, includingBars, includingPanels)