3 ms·
A little bit OT. I tried to go back to Firefox as I wrote an internal tool for company. Two problems did not go well: a) Firefox failed to provide a reasonab
by ttflee 12y ago
A little bit OT.
I tried to go back to Firefox as I wrote an internal tool for company. Two problems did not go well:
a) Firefox failed to provide a reasonable size for SVG elements, and by calling getBBox() I got a bounds that is not cropped by the container frame but the inner one which has been extended by elements drawn into, whereas in Safari/Chrome I could just call .offsetWidth/.offsetHeight;
b) I cannot view node data as quickly as I could in Safari/Chrome and this is a pain when debugging __data bound in D3.js. Maybe I will try installing Firebugs later.
For now I guess I have to stick to Chrome-first strategy or just ship it with nw.js.