Bug 301871 - DOM Range instances are missing required comparison constants
Summary: DOM Range instances are missing required comparison constants
Status: RESOLVED FIXED
Alias: None
Product: konqueror
Classification: Applications
Component: khtml ecma (show other bugs)
Version: 4.8.0
Platform: Microsoft Windows Other
: NOR minor
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-14 00:07 UTC by Tim Down
Modified: 2022-12-21 09:21 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Down 2012-06-14 00:07:47 UTC
DOM Range instances in KHTML do not have comparison constants START_TO_START, START_TO_END, END_TO_START and END_TO_END as required by the DOM4 Range spec. These constants are supported by KHTML as properties of the Range constructor, however.

The situation in DOM Level 2 is slightly confusing: the IDL definition in the main Range spec (http://www.w3.org/TR/DOM-Level-2-Traversal-Range/ranges.html#Level-2-Range-Interface) requires the constants to be present as properties of Range instances while the ECMAScript bindings page omits them (http://www.w3.org/TR/DOM-Level-2-Traversal-Range/ecma-script-binding.html#Range-ECMA). However, DOM4 is explicit and all other major browsers implement comparison constants as properties of Range instances, so KHTML should too.

References:

http://www.w3.org/TR/2012/WD-dom-20120105/#interface-range
http://www.w3.org/TR/DOM-Level-2-Traversal-Range/ranges.html#Level-2-Range-Interface
http://www.w3.org/TR/DOM-Level-2-Traversal-Range/ecma-script-binding.html#Range-ECMA

Reproducible: Always

Steps to Reproduce:
Run the following JavaScript in a web page:

"START_TO_START" in document.createRange()
Actual Results:  
Returns false

Expected Results:  
Returns true
Comment 1 Andrew Crouthamel 2018-11-09 01:01:37 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-18 03:30:25 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2022-12-20 22:51:38 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Tim Down 2022-12-21 09:21:24 UTC
I thought KHTML was abandoned. Anyway, I just tried it in the latest Konqueror, created a range and it had the constants, so I guess this issue is resolved.