Ben Kremer
Ben Kremer
@martyns0n There's not really a good way to solve this use case for the v1 API unfortunately :/ Another reason why I'm really focused on shipping v2 at the moment...
Oops, so I was in fact missing something I just realised: @Icebreaker9697's steps were completely right, since the changes you want need to be merged into the full tree (so...
Hi @jeffmath, Apologies that it's taken me absolutely forever to thank you for this! I'm committing to finally shipping a much improved v2 in the coming weeks, and your fork...
Thanks so much for explaining this issue for everyone @ankero 🙏 I'm going to pin this great explanation and add a link to the issue in the readme. Sorry for...
<foreignObject> doesn't seem to have the same result in Safari/Firefox as it does in Chrome browsers
> For Safari Browsers, I found out that in ForeignObjectElement.jsx, the width and height set in overwrites the prop's foreignObjectWrapper.style.width and ...height. Ah man, sorry about this (and my very...
<foreignObject> doesn't seem to have the same result in Safari/Firefox as it does in Chrome browsers
Please note that #284 may be related to this. I'm still going to remove the base margins for v2, but if you're seeing odd behaviour in Safari it may also...
Hi @matthewshim-ms, Yes you're spot on here; the docs have become messy & rather opaque over time due to too many ad-hoc additions to the v1 API (basically, my initial...
Glad you found it 👍 I'll leave this open until the new docs are ready as the de facto reference issue for the `v2` docs. Please feel free to follow...
Hi @tomashodek & @edo, Thanks for originally filing this issue and bringing it to my attention again now. I've finally found a good chunk of time to address issues and...
Hi @j-barata, Apologies for the delayed response! This isn't currently possible but I'll take this as a feature request :) For now I'm going to prioritise resolving #46 and #8...