The Flat Earth Society
The Flat Earth Society => Suggestions & Concerns => Topic started by: Thork on July 31, 2015, 09:05:07 PM
-
The site has compatibility issues with MS Edge, at least for me. I can't select any smileys or text features. I have to tag everything. :(
Can others check if this just is me?
If it isn't, the site admin must immediately address this. Potential flat earthers will be descending here from around the world using the latest technology from Microsoft, and we must be able to cater to their sophisticated needs.
-
It probably isn't compatible with Netscape Navigator, either. Surely we should modify the site to accommodate people's terrible choice in browser.
Also, I think its pretty funny that you didn't tag things by hand anyway. I was unaware that anyone who uses this site more than three times a year bothers clicking those buttons.
-
I have no idea what Edge even is. Care to provide some explanation as to why it needs to be treated specially?
-
This site may have some limitations but it's certainly better than that "other" FES site.
-
I have no idea what Edge even is. Care to provide some explanation as to why it needs to be treated specially?
Its the newest version of Internet Explorer. It's called Edge because Microsoft is trying to distance themselves from the negative connotations that Internet Explorer incurs.
-
This sounds like a flaw in edge moreso than a flaw here.
-
Anyway, it will soon be the world's most popular browser, so the site needs to be fixed.
-
Anyway, it will soon be the world's most popular browser, so the site needs to be fixed.
Care to provide some explanation as to why it needs to be treated specially?
-
Let's assume Chrome made a new release, and users with Chrome found the site to be broken. Would you make a fix?
Microsoft will get a large portion of people onto Edge. It actually benchmarks faster than Chrome and Firefox. Its ... not bad. It will also allow extensions soon too, making it every bit as good as other browsers to use. And websites are going to need to adapt. Like this one.
On another note, I know you pride yourself on how efficiently and well this site runs. People are going to arrive here and find stuff broken. And I know that is going to annoy you. So you've been informed, you can choose to ignore this bug issue, but I'm confident it will eat away at you until you work out why Edge works differently, fix the issue and inform the rest of the world via GitHub.
And with that ... I am finished with this thread, unless I need to come back and say thank you later.
-
Let's assume Chrome made a new release, and users with Chrome found the site to be broken. Would you make a fix?
That depends on the nature of the breakage. If it's caused by a bug in Chrome, I would file a bug report with Chromium and they would get another update out to fix the problem.
Microsoft will get a large portion of people onto Edge. It actually benchmarks faster than Chrome and Firefox. Its ... not bad. It will also allow extensions soon too, making it every bit as good as other browsers to use. And websites are going to need to adapt. Like this one.
Sorry, but the world doesn't need to adapt to every new piece of crapware Microsoft releases. The code that inserts smileys and formatting is standard Javascript that works across all browsers. If Microsoft have broken their Javascript implementation in Edge, they should probably fix that.
I'm not ruling out that it might be a problem with SMF, but I have no way of reproducing the behaviour as I have no Windows systems. Until somebody provides a more detailed problem report than "it doesn't work!" followed by a demand for us to fix it, there's no way I can even begin to investigate.
On another note, I know you pride yourself on how efficiently and well this site runs. People are going to arrive here and find stuff broken. And I know that is going to annoy you. So you've been informed, you can choose to ignore this bug issue, but I'm confident it will eat away at you until you work out why Edge works differently, fix the issue and inform the rest of the world via GitHub.
And with that ... I am finished with this thread, unless I need to come back and say thank you later.
So far, you're the only one to report this issue, despite not being the only regular using Windows 10. Unless somebody else comes forward to say they see the same problem, I'm going to assume it's an issue on your end.
-
I would try to reproduce the issue, but apparently Microsoft only provides Edge to Windows 10 users. That must be really fun for web developers.
-
This might be a dumb question, but is it possible that Thork does not have Java enabled or some other setting in Edge?
-
This might be a dumb question, but is it possible that Thork does not have Java enabled or some other setting in Edge?
There are no dumb questions where Thork is concerned. Assuming you mean Javascript, that would indeed cause this behaviour.
-
I just wrote some javascript and jquery to pull some apis from a server I have access to. Ran it in the browser, got the correct returns.
JavaScript and JQuery are both operating fine on my machine.
-
...why don't you just use Chrome or Firefox?
-
I'll test out the bug in a little bit. Wanted to mess around with Edge more anyway
Edit: It's a problem with Edge. It works perfectly fine in literally every other browser.
-
I've confirmed the bug, and yes it's only limited to Edge in Windows 10. Haven't spent any time troubleshooting yet, but will when I can if no one beats me to it. I don't think it's a critical issue, since it appears to be a JavaScript implementation issue in the browser. MS loves to be non-standard, regardless of their claims otherwise.
-
I've confirmed the bug, and yes it's only limited to Edge in Windows 10.
Edit: It's a problem with Edge. It works perfectly fine in literally every other browser.
Thank you Mr and Mrs Obvious. I am aware it is limited to Edge. That is why the thread is titled "Site not compatible with Edge".
Unless somebody else comes forward to say they see the same problem, I'm going to assume it's an issue on your end.
Well you can see where assumption got you. You get paid to solve IT problems right? You must be a joy to work with. Should I try turning my computer off and back on again?
-
I've confirmed the bug, and yes it's only limited to Edge in Windows 10.
Edit: It's a problem with Edge. It works perfectly fine in literally every other browser.
Thank you Mr and Mrs Obvious. I am aware it is limited to Edge. That is why the thread is titled "Site not compatible with Edge".
Unless somebody else comes forward to say they see the same problem, I'm going to assume it's an issue on your end.
Well you can see where assumption got you. You get paid to solve IT problems right? You must be a joy to work with. Should I try turning my computer off and back on again?
Parsifal asked for additional confirmation, because you have been known to be borderline retarded on occasion.
It will get fixed, most likely by Microsoft patching their PoS browser. I'll analyze using Fiddler in several browsers to see where Edge is fucking up when I have time.
-
Thank you Mr and Mrs Obvious. I am aware it is limited to Edge. That is why the thread is titled "Site not compatible with Edge".
Maybe it would be more accurate to say that Edge is not compatible with this site.
-
Well you can see where assumption got you. You get paid to solve IT problems right? You must be a joy to work with. Should I try turning my computer off and back on again?
Just turning it off might work out better for everyone.
-
Well you can see where assumption got you. You get paid to solve IT problems right? You must be a joy to work with. Should I try turning my computer off and back on again?
Just turning it off might work out better for everyone.
Please keep it civil in the upper fora.
-
Have you tried it on any other SM powered forum?
-
Good idea Dave, lets make this compatibility problem the user's issue. ::)
-
Good idea Dave, lets make this compatibility problem the user's issue. ::)
By checking other sites, you can determine if it's SM's code (and thus nothing Parsifal is responsible to fix) or modifications this site has had.
-
I was able to both decipher (seriously, Thork, try to be less unhelpful) and reproduce the problem. None of the js-driven buttons seem to work when posting from Microsoft Edge. This appears to be a shared problem between a number of current SMF forums that I tried. I'll try to figure out what's going on soon.
-
OMG posting this in the Edge browser and clicked the following buttons...
:) ;) :D ;D >:( :( :o 8) ??? ::) :P :-[ :-X :-\ :-* :'( >o< :-B
Unfortunately, that is with the user agent string set to IE 11. Microsoft's built-in debug tool shows the following error when the user agent string is set to Edge (which is the default, of course):
"Unable to get property 'insertSmiley' of undefined or null reference"
And links to this wonderful MS resource:
https://msdn.microsoft.com/library/h62awd63(v=vs.94).aspx
Confirmed Edge for PoS.
-
Unfortunately, that is with the user agent string set to IE 11. Microsoft's built-in debug tool shows the following error when the user agent string is set to Edge (which is the default, of course):
"Unable to get property 'insertSmiley' of undefined or null reference"
That's actually fairly helpful, thanks. I've just made a quick fix to the production code; can you clear your cache, try again and let me know if the problem persists?
If that fixes it, I'll commit it to git and we can be done with this.
-
Unless Edge sucks at clearing its cache, the problem persists. The error described by Junker applies to smileys, other buttons (e.g. [b]) throws Unable to get property 'handleButtonClick' of undefined or null reference instead while font selection menus throw Unable to get property 'handleSelectChange' of undefined or null reference
It highlights the following lines of code as the source of the problems, but it neglects to specify where they are located:
oEditorHandle_message.insertSmiley(oProperties)oEditorHandle_message.handleButtonClick(oProperties)oEditorHandle_message.handleSelectChange(oProperties)
Sorry, I'm currently in a setting where I literally cannot grep, but that should hopefully be of some use.
Edit: BUT WAIT, THERE'S MORE!
Trying to insert a quote while editing results in Unable to get property 'bRichTextEnabled' of undefined or null reference, and actually specifies the location of index.php (1265,6)
-
Jesus, Microsoft. I don't even have to be super fluent with code to know that this is very, very stupid.
-
To be fair, JS not having one consistent implementation is one of the main reasons people hate it. Then again, this is usually only a hypothetical problem...
-
To be fair, JS not having one consistent implementation is one of the main reasons people hate it. Then again, this is usually only a hypothetical problem...
Edge was literally built on the assumption that JS is the language of the Internet though :(
-
So we have confirmed that it isn't just me and that we know it is Edge unable to deal with the current JS that makes all the SMF buttons work.
Which I pretty much said 2 pages ago in my OP. Is anyone likely to try and fix this, or was this just an exercise in verifying if what I said was true for the sake of laughing at Microsoft or laughing at me in a no lose crapfest of a thread?
-
What is there to fix? The problem is clearly Microsoft's. Submit a trouble ticket through them.
-
No, the problem is ours. If I was writing a website and needed it to be able to work with Internet Explorer 6, I can't write to Microsoft and whinge that they fix it because it hates the way I did my JavaScript. I make exceptions to deal with how that browser reads websites.
<!--[if IE 6]>
<script type="text/javascript" src="http://www.somesite.com/wp-content/themes/SGWI/scripts/DD_belatedPNG_0.0.8a-min.js"></script>
<script type="text/javascript">
// <![CDATA[
DD_belatedPNG.fix('.pngfix, img, #home-page-content li, #page-content li, #bottom li, #footer li, #recentcomments li span');
// ]]>
</script>
<![endif]-->
We need an Edge equivalent is all.
-
It is very much a Microsoft problem. Microsoft is responsible for ensuring its browser is backwards compatible with various sites, it should not be this site's responsibility to bend to the will of Microsoft just because it decides to be a special snowflake and create Internet Exploredge 18 - NSA Edition.
-
No, the problem is ours. If I was writing a website and needed it to be able to work with Internet Explorer 6, I can't write to Microsoft and whinge that they fix it because it hates the way I did my JavaScript. I make exceptions to deal with how that browser reads websites.
<!--[if IE 6]>
<script type="text/javascript" src="http://www.somesite.com/wp-content/themes/SGWI/scripts/DD_belatedPNG_0.0.8a-min.js"></script>
<script type="text/javascript">
// <![CDATA[
DD_belatedPNG.fix('.pngfix, img, #home-page-content li, #page-content li, #bottom li, #footer li, #recentcomments li span');
// ]]>
</script>
<![endif]-->
We need an Edge equivalent is all.
And that equivalent is? Have they released the code to make this work?
-
It is very much a Microsoft problem. Microsoft is responsible for ensuring its browser is backwards compatible with various sites, it should not be this site's responsibility to bend to the will of Microsoft just because it decides to be a special snowflake and create Internet Exploredge 18 - NSA Edition.
I can just see Microsoft bending to the will of the flat earth society. ::)
No, the problem is ours. If I was writing a website and needed it to be able to work with Internet Explorer 6, I can't write to Microsoft and whinge that they fix it because it hates the way I did my JavaScript. I make exceptions to deal with how that browser reads websites.
<!--[if IE 6]>
<script type="text/javascript" src="http://www.somesite.com/wp-content/themes/SGWI/scripts/DD_belatedPNG_0.0.8a-min.js"></script>
<script type="text/javascript">
// <![CDATA[
DD_belatedPNG.fix('.pngfix, img, #home-page-content li, #page-content li, #bottom li, #footer li, #recentcomments li span');
// ]]>
</script>
<![endif]-->
We need an Edge equivalent is all.
And that equivalent is? Have they released the code to make this work?
Have Microsoft written the JavaScript alternative for SMF forums to use? I'm guessing not Dave. Have a day off.
-
It is very much a Microsoft problem. Microsoft is responsible for ensuring its browser is backwards compatible with various sites, it should not be this site's responsibility to bend to the will of Microsoft just because it decides to be a special snowflake and create Internet Exploredge 18 - NSA Edition.
I can just see Microsoft bending to the will of the flat earth society. ::)
No, the problem is ours. If I was writing a website and needed it to be able to work with Internet Explorer 6, I can't write to Microsoft and whinge that they fix it because it hates the way I did my JavaScript. I make exceptions to deal with how that browser reads websites.
<!--[if IE 6]>
<script type="text/javascript" src="http://www.somesite.com/wp-content/themes/SGWI/scripts/DD_belatedPNG_0.0.8a-min.js"></script>
<script type="text/javascript">
// <![CDATA[
DD_belatedPNG.fix('.pngfix, img, #home-page-content li, #page-content li, #bottom li, #footer li, #recentcomments li span');
// ]]>
</script>
<![endif]-->
We need an Edge equivalent is all.
And that equivalent is? Have they released the code to make this work?
Have Microsoft written the JavaScript alternative for SMF forums to use? I'm guessing not Dave. Have a day off.
No, has Microsoft released the JS specific command that is equivalent to
oEditorHandle_message.insertSmiley(oProperties)
I'm sure it's not an uncommon command.
-
So we have confirmed that it isn't just me and that we know it is Edge unable to deal with the current JS that makes all the SMF buttons work.
Which I pretty much said 2 pages ago in my OP.
Wrong on three counts. That's not what you said in your OP, and we've confirmed a lot more than what you said in your OP, including what the specific error message is. We've also confirmed that it does work with Edge if you switch to using the IE user agent, which proves your assertion that Edge is unable to deal with that Javascript wrong.
Posts like these are worse than useless; they are counterproductive because they add nothing new and create confusion by incorrectly summarising the situation.
Is anyone likely to try and fix this, or was this just an exercise in verifying if what I said was true for the sake of laughing at Microsoft or laughing at me in a no lose crapfest of a thread?
I've already tried to fix it. My fix evidently didn't work, although SexWarrior has since provided me with more detailed error information which may or may not help put together a correct fix. I don't know when I'll have time to do that.
I appreciate that you took the time to ignore my efforts so far, but can you please refrain from posting just to complain that we're not doing what we are doing? It's bad enough that your original report was devoid of any helpful information, you don't need to go derailing this thread now that we're trying to address the issue.
No, has Microsoft released the JS specific command that is equivalent to
oEditorHandle_message.insertSmiley(oProperties)
I'm sure it's not an uncommon command.
That's unlikely to be the line which has the actual problem. The error message is "Unable to get property 'insertSmiley' of undefined or null reference", which implies that oEditorHandle_message is undefined or null. Since that variable is set within Javascript in SMF, it's reasonable to suppose that it never gets set, either due to an error elsewhere on the page, or (as the error information provided by SexWarrior suggests) that Javascript not even being run.
-
So why would it work on all other browsers but not Edge?
Think MS disallowed null JScript object creation?
-
Another interesting note is that it also works when the user agent string is set to Edge Win 10 Mobile. If I remember correctly, the implementations were supposed to be the same.
-
So why would it work on all other browsers but not Edge?
Think MS disallowed null JScript object creation?
SexWarrior showed me something which seems to indicate that inline Javascript is being blocked by CORS policy. Naturally, this sounds too pants-on-head retarded even for Microsoft, but it would explain the symptoms observed. It would need to be done conditionally on the user agent setting, which is even more bizarre.
I doubt this will be a quick fix, so I probably won't get time to confirm or deny this hypothesis until at least the weekend.
-
To the administrators:
There may be some compatibility issues on this website but the response time is certainly better than the other FES website. From viewers like us. Thank You !
-
I figure this will all be solved when plugins are introduced. I imagine "Old JavaScript Compatability" will be near the top of whatever store there is for plugins.
-
I would hope that this wouldn't *need* a plugin. Basic JS support should be a given in a browser that explicitly advertises how much it loves JS.
-
I'm monitoring the SMF 2.1 Beta repository and the SMF Support Forums for potential fixes. They're aware of the situation and they might have a solution (as per this post (http://www.simplemachines.org/community/index.php?topic=538707.msg3831670#msg3831670)).
Unfortunately, they don't seem to specify what their proposed solution is, so we can't adopt it early. I suppose the good news is that it will be fixed eventually.
-
After a bit of drama on the SMF forum, this should now be fixed. Please let me know if anyone observes any uncommon behaviour from the editor window after this change.
Note that in most cases the relevant script will have been cached by the browser. You may need to clear the cache to see it take effect.
Let's keep the thread open for now in case there's any feedback, but this should be safe to close in a few weeks.
-
It works! Good job guys.
Now if you can fix animated avatars and resizing of avatars ... ;)
-
Your animated avatar is working.
-
Your animated avatar is working.
And that required much messing around and a loss of resolution when I shrunk it.
-
Your animated avatar is working.
And that required much messing around and a loss of resolution when I shrunk it.
Mine worked fine the very first time I tried it. Are you sure you are not complaining about Windows making it hard to make an animated avatar or something like that? I am failing to see what you are complaining about this time.
-
The forum has bugs when uploading. The admins know ... it is just a pain to fix.
This thread can be closed. The original issue is solved.
-
[...] Please let me know if anyone observes any uncommon behaviour from the editor window after this change.
[...]
Let's keep the thread open for now in case there's any feedback, but this should be safe to close in a few weeks.