excanvas & google closure VML
NikVdW
new member here, with a problem that has me stumped for the last
couple of days: I have ported most of my site over from jQuery to the
recently open-sourced Google Closure API.
One of my UI widgets relies on the Gauge visualization from Closure
API. This works fine in IE, as long as I force IE7 compatibility mode.
The Closure API's graphics library is smart enough to detect which
browser is in use, and then uses VML, SVG, or Canvas to draw the
graphics.
I also still need to use jQuery, as I rely on flot for a lot of
graphs. For this component, excanvas is required...
It is this combination that kills my site on IE. Excanvas seems to
mess with the Closure API's VML code... Is this possible? Is there a
way to exclude certain DOM elements from excanvas manipulation?
Basically, I only want excanvas to work on the flot graphs, not on the
Closure Gauges (which are rendered in VML anyway).
I hope this makes any sense,
thanks,
Nik.
NikVdW
as a follow-up to my original post, it seems that excanvas reduces the
size of my dynamically inserted VML elements (g_vml_ tags) to 4x4
pixels. Is there any way to avoid this?
thanks,
Nik.
Erik Arvidsson
My main suspicions are:
1. The namespace prefix is conflicting
2. The CSS is conflicting
3. The document.namespaces magic is conflicting.
> --
> You received this message because you are subscribed to the Google Groups "google-excanvas" group.
> To post to this group, send email to google-...@googlegroups.com.
> To unsubscribe from this group, send email to google-excanv...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/google-excanvas?hl=en.
>
>
--
erik
NikVdW
thanks for your reply. I've found a temporary workaround by removing
the #default#VML argument from the namespaces call in the excanvas
init code, and forcing my document mode into IE7 (meta tag)... Not
ideal as the root cause is probably somewhere else, but it works for
now.
thanks,
Nik.