293249 - Don't pretend to support canvas when cairo isn't built

Status: RESOLVED WONTFIX

(Core :: Graphics: Canvas2D, defect)

Description

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

We should not pretend to support canvas by instantiating nsHTMLCanvasElements
when cairo isn't built. Then we should use fallback and render the contents of
the canvas element instead.

We should just instantiate nsHTMLDivElement and not even build
nsHTMLCanvasElement.cpp or nsHTMLCanvasFrame.cpp. We could even kill the various
interface files maybe.

IMHO the parser changes could be left as is always though to avoid cluttering up
the parser code. Just #define NS_NewHTMLCanvasElement to NS_NewHTMLDivElement

Comment 1

[Vladimir Vukicevic [:vlad] [:vladv] (needinfo me, slow to respond)]

I had code to do this, but we explicitly killed it based on a discussion with
breadan and others, since cairo won't be an optional dependancy for very long.

Comment 2

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

Are we including cairo on all platforms, including things like minimo and beos?

Comment 3

[Vladimir Vukicevic [:vlad] [:vladv] (needinfo me, slow to respond)]

No reason for this to block 1.8b4, IMO.

I don't know what the Minimo or BeOS plan is; but <canvas> and cairo are a core
part of Gecko..

Comment 4

[Stuart Parmenter]

we're requiring cairo everywhere now.  builds without cairo are now unsupported.