Simple Machines Community Forum

Archived Boards and Threads... => Archived Boards => SMF Feedback and Discussion => Topic started by: riker on March 20, 2009, 10:23:59 AM

Title: SMF 2.0 and IE8 Final
Post by: riker on March 20, 2009, 10:23:59 AM
Will the compatibility issues be fixed on RC2 or are will those be left for RC3 ?.

I'm having to use the compatility botton on IE8 to post on my site amongst other things so lots of our members will have issues.

EDIT: I see this has been moved from support even though I class this as a support issue
Title: Re: SMF 2.0 and IE8 Final
Post by: Deaks on March 20, 2009, 11:46:41 AM
well as RC2 should be becoming with a new theme then Id guess its been fixed :)
Title: Re: SMF 2.0 and IE8 Final
Post by: riker on March 20, 2009, 01:01:14 PM
Quote from: Runic on March 20, 2009, 11:46:41 AM
well as RC2 should be becoming with a new theme then Id guess its been fixed :)

So it was a theme issue?
Title: Re: SMF 2.0 and IE8 Final
Post by: karlbenson on March 20, 2009, 05:39:39 PM
Which specific issue are you referring to Riker?
Title: Re: SMF 2.0 and IE8 Final
Post by: riker on March 20, 2009, 08:06:03 PM
Quote from: regularexpression on March 20, 2009, 05:39:39 PM
Which specific issue are you referring to Riker?
After copying and pasting a large news article and then going back (to it to add a source) everytime I tried to type the cursor went straight to the top until I clicked compatibility
Title: Re: SMF 2.0 and IE8 Final
Post by: Antechinus on March 20, 2009, 08:51:46 PM
I imagine it will be fixed. IE8 actually uses, wait for it, W3 standards. Yes, that's right. After decades of wandering around with their heads up their butts the IE dev team was finally convinced to build IE8 along the same lines as every decent browser in the world today.

Mind you this only happened late in the development of IE8 and it only happened after the IE team announced that IE8 would use the IE7 standards, which of course are not W3 compliant. This announcement caused such a massive uproar, and such vehement condemnation from so many people around the world, that the IE team actually found the brains and guts to admit it was a terribly dumb idea. Amazing. I wouldn't have thought it was possible, and it's about time too.

What it means though is that anything coded to detect IE will attempt to apply corrections for IE's previous pestilential standards. This obviously will mess things up a bit in IE8, which is why the compatibility mode was included. In other words, it's Microsoft's f@#kup, not anyone else's.

Now that they have sorted themselves out I expect that sites, and software like SMF 2, will be recoded to suit. I'm not one of the devs but I think this is obviously what they would be planning to do, and browser sniffing isn't a big deal, so I would expect it would be sorted before  Final even if it isn't sorted by RC2.
Title: Re: SMF 2.0 and IE8 Final
Post by: riker on March 21, 2009, 09:55:37 AM
Thanks Antechinus, you know I'm getting this strange feeling that you aren't a fan of Microsoft  lol
Title: Re: SMF 2.0 and IE8 Final
Post by: karlbenson on March 21, 2009, 10:12:56 AM
We weren't currently aware of an issue with that.

It doesn't appear to be an issue with the cursor, but with the the scroller/scrolling

I tested both with wysiwyg and non-wysiwyg.
- IE7
- IE8 (with compatibility view aka IE7 mode)
- IE8 (standard)

It only seems to affect IE8 in non-wysiwyg mode.

After pasting in some content IE8 seems to reposition itself half way in the text box.

This appears to be an smf bug, because it doesn't affect other standard textareas like News, etc.
Like Antechnius said, it could be one of our if(IE) statements that needs to be altered so doesn't affect ie8.

P.S i tested with IE8 rc1 and once I upgraded to IE8 final. The same bug occurs. Although I'm glad to see MS fixed the moving/small textareas bug.

Edit* Added to the tracker http://dev.simplemachines.org/mantis/view.php?id=3354
Title: Re: SMF 2.0 and IE8 Final
Post by: MrPhil on March 21, 2009, 11:00:53 AM
Web sites should (if possible) never test for a specific browser (or worse, a specific version of a browser) and do different things based on that. Instead, they should test for specific capabilities (e.g., the existence of a given function, or a certain value returned from a call) and proceed from there. Admittedly, sometimes it's just impossible to test for, say, incorrect handling of some CSS or JS feature, and you have to go with asking who the browser is.

Assuming that all IE browsers behave the same way leads to problems, as it evidently shows with SMF 2 problems. Testing for specific versions is better, but some lesser-known browsers claim to be IE or one of the other big guys so they won't be excluded from the game (how many websites have you been booted out of because you weren't on IE6?). Unfortunately, if they are actually standards compliant, you can end up branching the wrong way and end up with poor rendering.
Title: Re: SMF 2.0 and IE8 Final
Post by: w0kie on May 23, 2009, 09:39:37 PM
Quote from: riker on March 20, 2009, 08:06:03 PM
Quote from: regularexpression on March 20, 2009, 05:39:39 PM
Which specific issue are you referring to Riker?
After copying and pasting a large news article and then going back (to it to add a source) everytime I tried to type the cursor went straight to the top until I clicked compatibility

Microsoft, more or less forced me to "upgrade" to IE8.  Now my posting large news articles makes the cursor jump all over the place in SMF 1.1.8.  Is there a fix?
Title: Re: SMF 2.0 and IE8 Final
Post by: Antechinus on May 23, 2009, 09:49:06 PM
Have you tried using compatibility mode? You can switch it on and off just for posting news articles until we have a fix for this bug. Riker said that sorted the bug for him (as noted in the post you just quoted).

By the way, you can also downgrade to IE7 if you happen to prefer it. IE8 will uninstall like any other browser. I've done this myself during testing.
Title: Re: SMF 2.0 and IE8 Final
Post by: Owdy on July 26, 2009, 05:43:03 AM
Quote from: regularexpression on March 21, 2009, 10:12:56 AM
Edit* Added to the tracker http://dev.simplemachines.org/mantis/view.php?id=3354
How do you fix this with SMF 1.1.10?
Title: Re: SMF 2.0 and IE8 Final
Post by: karlbenson on July 26, 2009, 10:13:29 AM
We currently haven't applied any fix for 1.1.x or 2.x branches.

The ones posted with the bug report so far only covered the full reply and not all the other textarea that potentially could be affected by it.
Title: Re: SMF 2.0 and IE8 Final
Post by: deathshadow on October 05, 2009, 06:14:51 AM
I have a second fix that actually WORKS (since that whole min-width/max-width nonsense did exactly two things - and Jack left town, took his **** with him)

Since they are width:99% + borders, you don't have to worry about clearing really...

float:left;
display:inline;

Tripping those two properties on a textarea appears to clear up the issue with percentage widths. As I said the whole min-width/max-width instead of width did nothing for me to fix the issue. Float+Inline did the trick right off.

When in doubt, remember the unholy quartet of IE bugfixes:

position:relative;
zoom:1;
float:left;
display:inline;
Title: Re: SMF 2.0 and IE8 Final
Post by: Aleksi "Lex" Kilpinen on October 19, 2009, 04:10:21 AM
Quote from: Owdy on July 26, 2009, 05:43:03 AM
Quote from: regularexpression on March 21, 2009, 10:12:56 AM
Edit* Added to the tracker http://dev.simplemachines.org/mantis/view.php?id=3354
How do you fix this with SMF 1.1.10?
ALL 1.1 + IE8 problems can be fixed with adding the meta tag telling IE to render as IE7 AFAIK...
Title: Re: SMF 2.0 and IE8 Final
Post by: Owdy on October 19, 2009, 04:19:07 AM
What is that meta tag?
Title: Re: SMF 2.0 and IE8 Final
Post by: Aleksi "Lex" Kilpinen on October 19, 2009, 04:21:26 AM
Quote from: Owdy on October 19, 2009, 04:19:07 AM
What is that meta tag?
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />

Just add it amongst all the other Meta lines in index.template.php of your theme :)
Title: Re: SMF 2.0 and IE8 Final
Post by: Owdy on October 19, 2009, 04:21:54 AM
Cool,thanks!
Title: Re: SMF 2.0 and IE8 Final
Post by: Aleksi "Lex" Kilpinen on October 19, 2009, 04:22:23 AM
No problem ;)
Title: Re: SMF 2.0 and IE8 Final
Post by: Arantor on October 19, 2009, 11:19:39 AM
I should note that this was committed to the SVN trunk for 1.1 series so that if (and only IF) a 1.1.11 release is necessary it will be included in the core themes. Note that this is not, invariably, added to custom themes.
Title: Re: SMF 2.0 and IE8 Final
Post by: Owdy on October 22, 2009, 02:36:46 PM
Okay, that doesnt make IE8 bug go away. Users still camplaining. Glad that actual bug is fixed.
Title: Re: SMF 2.0 and IE8 Final
Post by: Darkness7148 on December 31, 2009, 08:13:26 AM
Are you aware this is still a bug in SMF 2.0 RC2? A user complained today on my forum so I checked it out. Sure enough, you get bouncy text areas in IE8. Tested with Curve theme. Min and Max Width are applied but it makes no difference.
Title: Re: SMF 2.0 and IE8 Final
Post by: Arantor on December 31, 2009, 08:14:09 AM
It appears to be something MS changed in a later build of IE8 - the other fix for 1.1.x broke too.
Title: Re: SMF 2.0 and IE8 Final
Post by: Darkness7148 on December 31, 2009, 08:15:35 AM
So what is the solution? Should I just use the IE7 meta tag until it's fixed?
Title: Re: SMF 2.0 and IE8 Final
Post by: Arantor on December 31, 2009, 08:21:46 AM
That doesn't appear to work either, as that's the fix in 1.1.x that no longer seems to work.
Title: Re: SMF 2.0 and IE8 Final
Post by: karlbenson on December 31, 2009, 09:59:53 AM
Quote from: Darkness* on December 31, 2009, 08:15:35 AM
So what is the solution? Should I just use the IE7 meta tag until it's fixed?

Don't use compatibility mode.  Use standard IE8.
Title: Re: SMF 2.0 and IE8 Final
Post by: Arantor on December 31, 2009, 01:34:26 PM
*nods* Karl, note that users are reporting problems with compatibility mode. One report seems to suggest it needs to be the very last tag prior to </head> in order to function now.
Title: Re: SMF 2.0 and IE8 Final
Post by: smp420 on December 31, 2009, 02:14:42 PM
I am using
/* The main post box - this makes it as wide as possible. */
.editor
{
   width: 5000px;
   max-width: 96%;
   display: inline;


}


It is working fine for me
Title: Re: SMF 2.0 and IE8 Final
Post by: Darkness7148 on December 31, 2009, 03:46:11 PM
Well, I think I've fixed the problem. I changed the width of .editor in the CSS file to px instead of %. Seems to have solved it.
Title: Re: SMF 2.0 and IE8 Final
Post by: Antechinus on December 31, 2009, 04:09:16 PM
That's not really a solution for general use since most people run their sites fluid.
Title: Re: SMF 2.0 and IE8 Final
Post by: jackon on January 06, 2010, 10:09:35 AM
I try to add the META and to modify the CSS .editor, I have always the problem.
How can i fix this problem?
Thanks
> SMF1.1.11
Title: Re: SMF 2.0 and IE8 Final
Post by: Arantor on January 06, 2010, 10:16:16 AM
It should not be necessary in SMF 1.1.11; the meta tag should be being added automatically.
Title: Re: SMF 2.0 and IE8 Final
Post by: jackon on January 06, 2010, 10:43:56 AM
Same. Is it a problem of CSS?
Title: Re: SMF 2.0 and IE8 Final
Post by: Arantor on January 06, 2010, 10:45:35 AM
No, the meta tag isn't listed in the theme file. It'll pulled into the template elsewhere, but reports indicate that MS may have broken their own fix :S
Title: Re: SMF 2.0 and IE8 Final
Post by: draggy on March 02, 2010, 02:44:10 PM
Quote from: smp420 on December 31, 2009, 02:14:42 PM
/* The main post box - this makes it as wide as possible. */
.editor
{
   width: 5000px;
   max-width: 96%;
   display: inline;


}

This also worked for me, SMF2 RC2, it had max-width and min-width when using IE8, but the text box would still bounce around. Adding the "width: 5000px;" fixed it.
Title: Re: SMF 2.0 and IE8 Final
Post by: Antechinus on March 03, 2010, 02:52:22 PM
Just noting that I've removed the emulate-IE7 meta tag and that apparently fixes the problem on the latest IE8. So it seems Microsoft did break their own fix and you're better off without it now.