Dandello wrote on Jul 18^th, 2014 at 5:44pm:


I'm not the judge or the executioner... I'm just humble former IE beta test team member... Good old times when people could hit Ctrl-Pause/Break and see source code of Windows... lol...

Monni wrote on Jul 18^th, 2014 at 5:28pm:


I'm pretty sure the keyboard shortcuts on the Posting section qualifies as a single layout engine thing. 

Dandello wrote on Jul 18^th, 2014 at 5:09pm:


In my personal opinion, we should support all common features and avoid adding explicit support for features only available on one layout engine.
When I made the patch for IE, I intentionally implemented Trident check as secondary check, because that excludes automatically IE versions before IE 7 if not explicitly included on MSIE test.
For XMLHttpRequest, there was exception that worked on IE6, but not IE5.x and older, because IE6 does indeed support XMLHttpRequest.

Ideally we should be looking at evaluating support by browser function support - does it need ActiveX and what version is needed for the ajax call, does it support XMLhttp natively, are there ajax functions that aren't supported or need work arounds?

Do we really need to evaluate for keyboard shortcuts and MSIE specific features when more and more users won't see them much less use them? (And are not essential to YaBB's functionality.)

Dandello wrote on Jul 18^th, 2014 at 1:22pm:


It's more about supporting the current "big three" browsers (IE/Trident, Chrome/Blink, Firefox/Gecko) than trying to support all the future browsers... Many browsers share same layout engine, and for those same code should work.
I agree that trying to support too many browsers is a bad thing.
And don't shoot me for not mentioning Opera in big three, because it uses same layout engine as Chrome.

Browser detection by browser string is considered by many experts to be bad form and a lost cause - browsers change too quickly, new minor ones appear and disappear and in YaBB's case it means issuing patches and rewriting sections of embedded code to accommodate variations of a browser that doesn't always properly render standards compliant css and html anyway.

I think we need to dump the browser specific keyboard short cut keys and the iecopy function altogether.  With more and more people moving to mobile devices, fewer and fewer people are going to be able to use those functions anyway and I figure the rest of us can hit the 'Post Message' button too.

Dandello wrote on Mar 6^th, 2014 at 11:10pm:


IE 9, IE 10, and IE11 have different user agent strings because Microsoft was split as two companies, they also separate normal mode and compatibility modes... You can detect all of them if you compare the full user agent string and parse the part where it says Trident/n.n ... Some of the versions also identify itself as "IE nn.n" instead of "MSIE nn.n"

The numbers in Trident mean:

Trident/3.1 = IE 7.0
Trident/4.0 = IE 8.0
Trident/5.0 = IE 9.0
Trident/6.0 = IE 10.0
Trident/7.0 = IE 11.0

For example:

Quote:


This means running IE 11 on 64-bit Windows 7 in normal mode.
If number after Trident is smaller than in the respective table row above, it means IE is running in compatibility mode.

It breaks in such weird places. 

It took me many years to get away from MSIE. Now that I have been away from it, I find it hard to even use it for testing.

Found and implemented a fix for MSIE11. in ubbc.js find

function storeCaret(text) {
     if (text.createTextRange) text.caretPos = document.selection.createRange().duplicate();
 } 

and replace with

function storeCaret(text) {
     if ((window.ActiveXObject) && "ActiveXObject" in window) {
         if (text.createTextRange) text.caretPos = document.selection.createRange().duplicate();
     }
 } 

MSIE11 doesn't identify itself as MSIE, doesn't support ActiveX and doesn't ignore older MSIE specific javascript tags that 11 doesn't use. The other broswers just ignore them.

AAKK!
(The problem is with Preview and the character counter. To get MSIE11 to update them you currently have to click format button or close/open Preview.)
 

Edited: