Opened 16 years ago
Closed 16 years ago
#3529 closed Bug (fixed)
[IE] Wrong find matching in IE8 quirks
Reported by: | Tobiasz Cudnik | Owned by: | Garry Yao |
---|---|---|---|
Priority: | Normal | Milestone: | CKEditor 3.0 |
Component: | General | Version: | |
Keywords: | Confirmed IE Review+ | Cc: |
Description
Wrong find matching in IE8 quirks.
TC
- Use following content:
<p> ^a foo a</p> <p> a foo a</p> <p> </p>
- Open Find dialog
- Search for "foo"
Result:
<p> a ^foo a^</p> <p> a foo a</p> <p> </p>
Expected result:
<p> a ^foo^ a</p> <p> a foo a</p> <p> </p>
Does not take place in IE8 strict.
Attachments (3)
Change History (16)
comment:1 Changed 16 years ago by
Owner: | set to Tobiasz Cudnik |
---|---|
Status: | new → assigned |
comment:2 Changed 16 years ago by
Owner: | changed from Tobiasz Cudnik to Garry Yao |
---|---|
Status: | assigned → new |
comment:3 Changed 16 years ago by
Keywords: | Review? added |
---|---|
Status: | new → assigned |
This is an uncovered case of #3436, yet another browser sniffing mistake, the culprit is that the detection result of CKEDITOR.env.version == 7 under IE8 quirk will skip the fix for CKEDITOR.dom.text::splitText.
The idea fix should use feature detection instead.
Changed 16 years ago by
Attachment: | 3529.patch added |
---|
comment:5 Changed 16 years ago by
Keywords: | Review- added; Review+ removed |
---|
Warning: that trick to detect IE8 isn't safe.
in Firefox 3.5
Object.prototype.toString.call( self.JSON ) != "[object JSON]"
is false, so it will follow the IE8 code path although it doesn't needs it. As other browsers implement native JSON support they will also fail the test
Changed 16 years ago by
Attachment: | 3529_2.patch added |
---|
comment:8 Changed 16 years ago by
Keywords: | Review? added; Review- removed |
---|
Proposing a better way to detect this feature and centralize it into CKEDITOR.env.
comment:9 Changed 16 years ago by
The new detection method is more accurate for sure, but I'm not sure if the increased core code size is worth it.
comment:10 Changed 16 years ago by
Keywords: | Review- added; Review? removed |
---|
That's correct. We don't need to bloat CKEDITOR.env. It "already" offers all we need, and for this case, it's enough to check for IE8 inside the spli function. My previous concerns were about using the JSON object for detection.
This fix must be as simple as possible, and even the newly proposed detection system can be simplified.
Changed 16 years ago by
Attachment: | 3529_3.patch added |
---|
comment:11 Changed 16 years ago by
Keywords: | Review? added; Review- removed |
---|
I've reverted the detect to browser sniffing way, which include part of Tobiasz's approach at #3549 here for detecting ie8 with documentMode.
comment:12 Changed 16 years ago by
Keywords: | Review+ added; Review? removed |
---|
As discussed with Tobias, I'll take over this ticket to avoid overlapping at several recent related tickets.