User Profile

deuce789 · Oct 28 '07, 06:53 AM

regardless of what forum you post this on, doing this with javascript is absolutely impossible :-)

deuce789 · Oct 27 '07, 09:01 AM

Refer to this post:
Edit: link removed

deuce789 · Oct 26 '07, 08:12 AM

Yes, it can (with setAttribute) anyway :-)

deuce789 · Oct 26 '07, 04:08 AM

I understand where you are coming from dont get me wrong, but how compliant the outputted code from a wysiwyg editor is directly related to what browser the user is using and although internet explorer is the worst, all of the other browsers that support wysiwyg may be better with their output code, they are still far from perfect as far as following w3c standards 100%. God help us if a simple attribute can break a whole web page in the future....

deuce789 · Oct 25 '07, 12:24 PM

This is out of the scope of javascript. This popup window is an OS window and javascript only deals with stuff within the browser.

deuce789 · Oct 25 '07, 04:38 AM

why dont you try something like:

Code:

document.getElementById('id_phone').className = "my_red"

?

deuce789 · Oct 25 '07, 04:16 AM

Hi,

Thx for that link, reading it now.

In regards to wysiwyg browsing and how uncompliant the code is (in all browsers, but yes, in particular IE). This is actually a browser problem, because execCommand does whatever the browser is up for doing (this does change quite abit from browser to browser, and there is no control over this aspect). Any wysiwyg editor made that uses execCommand cannot be told to output clean code...

deuce789 · Oct 25 '07, 03:41 AM

Hi,

Sorry you may have misunderstood me ever so slightly, i am talking about the usage of being able to provide wysiwyg through javascript (not wysiwyg itself) and the fact that the code outputted from such an editor is not w3c compliant anyway, and due to the nature of the fact that the code outputted is not going to be even remotely compliant in internet explorer and still nowhere near compliant in all other browsers (including firefox)....

deuce789 · Oct 25 '07, 02:48 AM

Are you setting classes using setAttribute?

If so you need to use setAttribute("c lassname", "name_of_class" );
In internet explorer and setAttribute("c lass", "name_of_class" ); for all the other web browsers

deuce789 · Oct 25 '07, 01:57 AM

WYSIWYG editing itself was originally a microsoft only thing and in itself is "violation" of w3c standards, and from browser to browser the way it acts can be very different, so are you saying we shouldnt use WYSIWYG editing at all, because in this case it seems everyone and every browser maker followed microsoft and not the standards :-)

deuce789 · Oct 23 '07, 02:29 AM

There is indeed an attribute called unselectable, which was developed especially for problems like this, and was introduced in internet explorer 4.

http://msdn2.microsoft.com/en-us/library/ms536419.aspx

I actually have had the exact same problem myself with developing rich text editor related stuff.

This attribute is only valid in internet explorer and Opera (From version 7 onwards i believe), however it fixes...

deuce789 · Oct 22 '07, 12:38 PM

Hi,

This is a security measure in firefox to stop cross domain exploits, however you can still achieve the desired result by using a little "hack" so to speak.

Basically, the part of code that writes the content to the iframe (document.open, document.write, document.close) . If you split this off into a seperate function on its own, and delay it for a few seconds, the iframe will stay in the editor without disappearing....

deuce789 · Oct 22 '07, 12:32 PM

Solution:

You can use the following attribute to get around this problem.

Code:

 <div unselectable="on"></div>

This attribute can also be applied to table cells, etc etc

deuce789 · Oct 8 '07, 03:10 AM

without code its hard to say, but sounds like it isnt happening because of security permissions in these browsers (cross domain exploits is why this is usually not allowed)...

deuce789 · Oct 1 '07, 02:00 PM

This code always works in IE for me, try scrapping all your other code and try this:

ps: this is using the freeajax wrapper.

Code:

<script src=\"freeajax.js\" language=\"javascript\"></script>
<script>
function loadModule(val,win)
{
	ajaxSend("GET", "tabledeleterowscript.php?mdid="+val, "win", "innerHTML");
}

...

deuce789 · Oct 1 '07, 11:08 AM

i dont understand exactly what you mean either, however looking at your code, the ajax part seems very messy and over complicated. I use the following ajax wrapper which makes this kind of stuff easily possible with just one line of javascript compared to the large amount you have right now. I think you will find it will solve your problem.

FreeAJAX

deuce789 · Oct 1 '07, 10:02 AM

thank you for your help, saved me days figuring it out, all works perfectly now :)

deuce789 · Oct 1 '07, 09:18 AM

Hi,

I just gave this a shot, but unfortunately it yields the same results as just doing alert(i).

The last item in the loop is used, in this case 3. So regardless of which textarea i click on the result returned is always 3.

Thanks,
Steve

deuce789 · Oct 1 '07, 07:41 AM

Hi,

I tried this out and it appears to return the parent node within the editable iframe content, instead of the iframe itself.

Any other suggestions?

Thanks,
Steve

User Profile

Profile Sidebar

.htaccess regular expression question

Leave a comment:

Leave a comment:

Leave a comment:

Leave a comment:

Leave a comment:

Leave a comment:

Leave a comment:

Leave a comment:

Leave a comment:

Leave a comment:

Leave a comment:

Leave a comment:

Leave a comment:

Leave a comment:

Leave a comment:

Leave a comment:

Leave a comment:

Leave a comment:

Leave a comment: