FANDOM


  • Here are the release notes for FANDOM's code release scheduled for January 17, 2018:

    • BUGFIX: We will fix a mobile layout issue where collapsed sections could not be expanded on some older browsers.
    • BUGFIX: Rejected custom JS on Dev Wiki will no longer have a broken "[Why?]" link displayed. Thanks to KockaAdmiralac for this fix!
      Loading editor
    • BUGFIX: We will fix a mobile layout issue where collapsed sections could not be expanded on some older browsers.

      Is this go live yet?

        Loading editor
    • It will go live tomorrow (Wednesday).

        Loading editor
    • Honestly, FANDOM on older browsers really needs a lot of fixes, if Monobook was actually the only good skin in older browsers. Mercury is good enough with that fix, even though there are still a few minor layout issues. However, Oasis looks absolutely horrendous in older browsers, only because of the fact that there were extreme layout issues. The global navigation is messed up, the page header in general is messed up, the article content, comments and right rail modules are so far away from the page background and the Fan Feed is located at the right and not at the bottom. Hope we will be able to see these fixes for older browsers.

        Loading editor
    • Older browsers as in?

        Loading editor
    • Wii U browser, Safari in iOS 6 etc.

        Loading editor
    • JustLeafy wrote: Wii U browser, Safari in iOS 6 etc.

      Pretty sure all of those are unsupported.

        Loading editor
    • Sophiedp wrote:

      JustLeafy wrote: Wii U browser, Safari in iOS 6 etc.

      Pretty sure all of those are unsupported.

      Yeah, but I do think the bug about mobile H2s will be fixed in these browsers.

        Loading editor
    • JustLeafy wrote:
      Honestly, FANDOM on older browsers really needs a lot of fixes, if Monobook was actually the only good skin in older browsers. Mercury is good enough with that fix, even though there are still a few minor layout issues. However, Oasis looks absolutely horrendous in older browsers, only because of the fact that there were extreme layout issues. The global navigation is messed up, the page header in general is messed up, the article content, comments and right rail modules are so far away from the page background and the Fan Feed is located at the right and not at the bottom. Hope we will be able to see these fixes for older browsers.

      Those fixes will require staff to rewrite those things to not use Flexbox (Or to also include the old flexbox syntax as well as the new ones) and some old browsers such as Internet Explorer 9 does not support Flexible Box system and it is also unsupported. It also has a lot of design issues in Opera Mini but Opera Mini supports flexbox and therefore it is almost okay.

        Loading editor
    • The main targets for this fix were Safari 9 (on iOS) and older versions of Chrome (such as Chrome 40), though it probably fixed the behaviour on others as well.

      However, it is very unlikely that we will work on significant fixes for very old browsers like Safari 6 or IE9. Very few people are on them now, thankfully - and we would strongly recommend people switch anyway, due to the general security risks of using them.

        Loading editor
    • We've no special release notes for tomorrow's release (Thursday), so no new Technical Update post today.

        Loading editor
    • Kirkburn wrote:

      it is very unlikely that we will work on significant fixes for very old browsers like […] IE9.
      You can ignore IE9, Windows 7 fans like me upgraded to IE11 when IE9 allegedly/officially died, and for hardcore XP fans IE9 would be "too new", they (should) know where to find fresher browsers than IE8: Firefox 10esr was nice, last update in January, 2013; still working in a Windows 2000 VM (or FWIW also in a real Windows 7 ;-)
        Loading editor
    • A FANDOM user
        Loading editor
Give Kudos to this message
You've given this message Kudos!
See who gave Kudos to this message