#2437: V3: Environment and browser information
--------------------------+-------------------------------------------------
Reporter: fredck | Owner: fredck
Type: New Feature | Status: assigned
Priority: Normal | Milestone: CKEditor 3.0
Component: General | Version:
Resolution: | Keywords: Confirmed V3ProtoBase Review?
--------------------------+-------------------------------------------------
Comment(by fredck):
Replying to [comment:2 alfonsoml]:
> In order to be forward compatible, we should remember to try to avoid
using these properties as long as it's possible to detect just the bug
that we want to workaround as Hallvord reminded in
http://dev.opera.com/articles/view/a-browser-sniffing-warning-the-trouble/
. I mean: if we want to use window.foobar, then test for that feature,
instead of hardcoding right now that only browser X and Y does support it,
because the newer version of Z might also support it.
That's the way we already do it (see
[http://dev.fckeditor.net/browser/CKEditor/branches/prototype/_source/core/tools.js#L34
CKEDITOR.tools.globalEval] for an example). But you are correct to
remember to keep it in mind.
I've coded
[http://dev.fckeditor.net/browser/CKEditor/branches/prototype/_source/core/tools.js#L158
CKEDITOR.tools.htmlEncode] by using the "failure test" (not "feature
test") idea, which we can also consider. We must also consider the impact
in the code size that it brings.
> So we could have in the CKEditor.env object also a "features" section,
that does try to detect the main issues and use those instead of the
classic and generic "if (FCKBrowserInfo.IsIE)" (because then we need to
have IsIE6, IsIE7, IsIE8...)
I see the feature test thing as something to be done inline, when
implementing a feature. It's not clear to me how CKEDITOR.env could be
involved on this. Maybe an example could help me on that.
--
Ticket URL: <http://dev.fckeditor.net/ticket/2437#comment:5>
FCKeditor <http://www.fckeditor.net/>
The text editor for Internet
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
FCKeditor-Trac mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fckeditor-trac
