Closed Bug 469715 Opened 14 years ago Closed 14 years ago

re-factored the Position interface to contain the 'coords'

Categories

(Core :: DOM: Geolocation, defect, P1)

defect

Tracking

()

RESOLVED FIXED

People

(Reporter: dougt, Assigned: dougt)

References

()

Details

(Keywords: fixed1.9.1)

Attachments

(1 file)

As proposed at the f2f meeting in London, I have added the Coordinates
interface and re-factored the Position interface to contain the
'coords' attribute and the 'timestamp'.
Attached patch patch v.1Splinter Review
Attachment #355609 - Flags: superreview?(jst)
Attachment #355609 - Flags: review?(jst)
Flags: blocking1.9.1?
Flags: blocking-fennec1.0?
Comment on attachment 355609 [details] [diff] [review]
patch v.1

 interface nsIDOMGeoPosition : nsISupports
 {
+  readonly attribute nsIDOMGeoPositionCoords coords;
+  readonly attribute DOMTimeStamp timestamp;
+
+  /* This are deprecated and will be removed. */
   readonly attribute double latitude;
   readonly attribute double longitude;
   ...

Any reason not to just remove those right away?

r+sr=jst
Attachment #355609 - Flags: superreview?(jst)
Attachment #355609 - Flags: superreview+
Attachment #355609 - Flags: review?(jst)
Attachment #355609 - Flags: review+
Comment on attachment 355609 [details] [diff] [review]
patch v.1

i would love to remove these right away, but I am worried about existing web apps that use the old API.

any suggestions?
mc:b13132800742
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
mc:03b44f2b6f08  (forgot to add the new idl file.)
Flags: blocking1.9.1? → blocking1.9.1+
Priority: -- → P1
Keywords: fixed1.9.1
landed on 1.9.1, removing blocking-fennec request
Flags: blocking-fennec1.0?
You need to log in before you can comment on or make changes to this bug.