Status

()

defect
RESOLVED FIXED
14 years ago
14 years ago

People

(Reporter: cdbordelon, Unassigned)

Tracking

1.0 Branch
x86
Windows XP
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Reporter

Description

14 years ago
tracking bug for deer park release

Comment 1

14 years ago
Is this about the new Web Applications 1.0 CANVAS element?
Assignee: firefox → nobody
Component: General → Layout: Canvas
Product: Firefox → Core
QA Contact: general → layout.canvas
Version: unspecified → 1.0 Branch

Updated

14 years ago
Depends on: 288714

Updated

14 years ago
Depends on: 302566

Comment 2

14 years ago
I dont know where this belongs, so im putting it here.\

The safari/firefox canvas differences should be eliminated. i refer to the end tag requirement. The end tag should be required in safari. While implementing this now would break some pages, there would be very few pages that actually use <canvas> at this time, and because mozilla prides itself in standards, wouldnt it seem appropriate to have a standard between different products, especially considering their similarity? We shouldn't, as web developers, be needing to prefrom css hacks, just to get 2 browsers, made by the same organisation to work with each other, its crazy. We are already fighting with all ther other browsers on the planet, theres no need to intorduce complexity.
(In reply to comment #2)
> We shouldn't, as web developers, be
> needing to prefrom css hacks, just to get 2 browsers, made by the same
> organisation to work with each other, its crazy. 

Erm, I think you're confused.. Safari is developed by Apple, built on top of KHTML.  Firefox is developed by us, built on top of Gecko.  Gecko already requires a close tag.. it sounds like you want to file a bug with Apple.
Josh: http://webkit.opendarwin.org/ is accepting bugs and patches.

/be
old bug -> fixed
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.