You are not logged in.
Use the pageStyle configuration option, i.e.
xinha_config.pageStyle = ''img {padding: 5px}";
in your config file.
You don't need any quotes around the url. Just
<div style="background: url(http://some.domain.here/image.file.here)">test</div>should work with no problems.
Updated in changeset:1235
If you still have svn commit access, you could simply change the license in the pluginInfo to HTMLArea. The files both already contain credits to the original authors, so I wouldn't think you need to change anything else, unless you want to. If you don't have access, I think your post above is sufficient to permit someone else to do it for you. Thanks!
Found it. I was looking at an older version of ListType. It's exactly the same situation as CharacterMap. Mokhet released his modifications as creative commons for both of them.
I just did some checking, and found that the original version 1.0 of CharacterMap was released under the htmlarea license by Holger Hees and Bernhard Pfeifer for System Concept GmbH & Bernhard Pfeifer (http://www.systemconcept.de/). Version 2.0 was made by mokhet (Laurent Vilday) and released under the creative commons license. I'm wondering if that was valid, to change the license in that way, and maybe we should just change it back. Or try to get in touch with mokhet and get him to change it.
Also, the ListType plugin was written by mishoo (Mihai Bazon) and released under the htmlarea license, according to the pluginInfo in the file itself. Where does it say creative commons?
%2F is the url encoding for "/".
You need to point the script to the textarea. Change 'myTextArea' to 'newbiearea1' in the xinha_editors array.
Just follow the NewbieGuide. It's the same for all supported browsers.
You can browse the repository at http://xinha.webfactional.com/browser. Look in the 'trunk' folder.
If you study the code in the subversion repository rather than the compressed distribution files you will have an easier time figuring out how the code works.
Another approach that I have used is to use css positioning to place the editor outside the window during loading, i.e.
style="position:absolute; left: -2000px"
and then move it back into the window with a script when needed. This avoids having the editor appear briefly during loading before you hide it.
I think you are seeing this bug: http://xinha.webfactional.com/ticket/1112. Try upgrading to the latest nightly version.
Your best option is probably to deal with it in your server-side script: translate %5eaccountdomain%5e back to ^accountdomain^.
I have noticed this problem recently also. It looks like the FullScreen plugin is not loading properly if there are many editors on the page. (Notice that when this happens the Full Screen button is missing from the toolbar.) I have opened a ticket for this: http://xinha.python-hosting.com/ticket/1048
Try
xinha_config = new Xinha.Config();
xinha_config.width = '333px';
xinha_config.height = '394px';
FF is fussy about units.
The problem is most likely that tt is always null, i.e. the program never finds the existing <tt> and therefore always executes the "else" branch.
If you are using the standard Xinha.css style sheet, you can actually omit all references to style sheets in your configuration and XinhaCore.js will just go find it. If you have your own style sheet, you use
_editor_css = "myStyles.css"
(with path if necessary). In either case, you don't need a <link> tag any more.
We really need to update the documentation on this....
The mechanism for invoking style sheets and skins changed. See http://xinha.python-hosting.com/ticket/1026.
The changes in your first post just define a couple of new regexps, without actually using them. You need to expand the statement that starts on line 154 (in the original source) to invoke them.
You must be using the getHtml plugin, because the built-in getHtml() function doesn't support the <area> tag (ticket #551). The getHtml plugin was designed to produce XHTML code, but you should be able to get rid of the backslashes by commenting out line 75:
// replace(c[4], '<$1$2 />').//terminate singlet tagsI haven't tried this, so I don't know what other problems it might cause.
IE now renders those two images with a small gap in-between them...
This was corrected in the most recent version of the getHtml plugin (changeset:601).
I have posted an enhanced version of color_picker.js as an attachment to ticket #85 (http://xinha.python-hosting.com/ticket/85) which fixes the problem with <select> elements, among other things. I would welcome comments on the enhancements before I commit the changes.
See ticket #85.
Xinha works just fine on Macs and always has since Mozilla 1.3 and Firefox 0.7.