Changes between Version 5 and Version 6 of Compatibility


Ignore:
Timestamp:
Feb 13, 2014, 12:45:29 PM (11 years ago)
Author:
Piotrek Koszuliński
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Compatibility

    v5 v6  
    11= Compatibility =
    22
    3 (Outdated!) See: [http://docs.ckeditor.com/#!/guide/dev_browsers CKEditor V4 Graded Browser Support]
    4 
    5 == Browsers ==
    6 
    7 Theoretically we should support every browser that offers editing features in the DOM, which today includes IE, Firefox, Opera and Safari (maybe Konqueror? ... still to check).
    8 
    9 It is a fact instead that Opera and Safari are still buggy to be able to be supported today, so we must work to inform the developers of those browsers about their issues, and pray to have fixes soon.
    10 
    11 Whenever a new version is to be released, a complete test should be done over all supported browsers.
    12 
    13 === IE ===
    14 
    15 This is the most used browser in the marketplace. Today we are supporting version 5.5, 6 and 7 (small fixes in the SVN yet).
    16 
    17 === Firefox ===
    18 
    19 The second most used browser. We are still offering support for the buggy Firefox 1.0.x. As have already supporting two new generations after that (1.5 and 2.0), I believe we could seriously thing about stop supporting 1.0.x, as it introduces specific (and not always so nice) code to the editor.
    20 
    21 === Opera (not supported yet) ===
    22 
    23 We are very close to be compatible with its latest builds.
    24 
    25 FredCK has a NDA signed with Opera, to have access to the latest builds, bugs tracker and other developer's resources at Opera. Hallvord R. M. Steen, from Opera, is part of the project as our "Opera Advisor". They have always wanted to give us full support. We have many bugs reported at their ticketing system.
    26 
    27 There is a specific milestone called "Opera Compatibility" at our Trac site. We are all invited to test this browser as much as we can, and fill tickets for found issues.
    28 
    29 If any current bug is related to an Opera bug, please attach a reduced test case to the ticket and FredCK will report it to their ticketing system.
    30 
    31 === Safari (not supported yet) ===
    32 
    33 It is very important to support Safari today. Not because of the users base, but as a marketing thing. But this browser is still too buggy. You may find other editor proposing Safari support out there just to get the attention, but is well known how buggy they are with this browser. We will declare FCKeditor compatible to it as soon as we have a solid and stable situation.
    34 
    35 The nice news is that we are having good results with the [http://nightly.webkit.org/ latest nightly build of WebKit].
    36 
    37 There is a specific milestone called "Safari Compatibility" at our Trac site. We are all invited to test this browser as much as we can, and fill tickets for found issues.
    38 
    39 If any current bug is related to a Safari bug, please open a bug report at [http://bugs.webkit.org/ WebKit's Bugzilla]. If the bug is something that we can't easily find an easy workaround, please make the [http://bugs.webkit.org/show_bug.cgi?id=9915 FCKeditor Master Bug] dependent of your new bug.
    40 
    41 ----
     3**See [http://docs.ckeditor.com/#!/guide/dev_browsers CKEditor Browser Support guide].**
© 2003 – 2022, CKSource sp. z o.o. sp.k. All rights reserved. | Terms of use | Privacy policy