@simonw I would use OffscreenCanvas instead of creating <canvas> element. No need to parse the viewBox (there is DOM API for that). Exact file size could be determined from the bitmap blob.
The "Export" panel in Boxy SVG version 4.41 has been redesigned, featuring several new capabilities. These include: bulk export, multi-page PDF export, per-object export settings, size variants and more.
Explore these new features in the live demo at https://t.co/xFpNtKnIpW
@hugolatra@Grummz@Adobe Currently only the Linux app is free, though the plan is to switch to a freemium model on all platforms: https://t.co/cUHBhDZhxl
Here it is. If you are a professional, if you are under NDA with your clients, if you are a creative, a lawyer, a doctor or anyone who works with proprietary files - it is time to cancel Adobe, delete all the apps and programs. Adobe can not be trusted.
@LeaVerou Some other notable improvements from the past years that come to my mind:
- Wide gamut colors
- 3D transforms (Safari)
- Blend modes
- Variable fonts
- Multiple filters per element (Chrome)
- Filter functions (Chrome)
@LeaVerou For me the biggest problem with SVG animations was fixed with the introduction of transform-origin/transform-box combo. I was surprised to discover that Chrome and Safari made these properties compatible with animation elements. Huge improvement, but it went almost unnoticed.
Boxy SVG v4.32.0 adds support for all color spaces from CSS Color Level 4. This feature was made possible thanks to the fantastic https://t.co/Eid5ZwPRqr library by @LeaVerou and @svgeesus. For the live demos check https://t.co/dUZXxenHg3 and https://t.co/gMN0ZFqK4L
We’ve always told web devs that browsers prioritize what to implement based on developer demand.
There is one exception: SVG.
SVG is used on >65% of websites. Yet, browsers have been *refusing* to work on SVG, ignoring pressure and pain points from web devs.
#StateOfHTML showed SVG as the top content pain point: https://t.co/bWwah7tV3I
Tons of work (SVG 2, fill & stroke, and more) has sat unimplemented for years. At this point, in standards circles, we know not to touch SVG with a barge pole.
Case that prompted this post, Custom SVG elements. 7y of pressure, a cornucopia of use cases, yet “no implementer interest”: https://t.co/6Gh72iFwMg
Can someone shed some light on why browsers are so desperate to kill SVG?
Because at this point, I refuse to believe this is just a rational business decision based on hard facts. The hard facts are shouting “Fix your damn implementations!” and browsers are going "la-la-la" 🙉🙉🙉
@diekus @dannymoerkerke From my testing PWA tab strips don't seem to be usable on any desktop platform as of Chrome 122. On Windows and Linux I couldn't make them to show at all, even with experimental flags enabled.
@samirmulla710@CocoMaterial@typesense Currently only the Linux app distributed on Flathub is available for free. The web app will be distributed using freemium model in future: https://t.co/cUHBhDZhxl
@anatudor The way how percentage units are handled in SVG is just broken and their usage should be discouraged. In most scenarios you can achieve the same effect with user units in object bounding box space.
@anatudor I hope you also didn't miss the fact that if you put your line inside a <pattern>, the percentages will be resolved relatively to the view box of the closest <svg> rather than of the closest <pattern> (assuming that browser follows the spec).
@DaviesMediaDes@inkscape Boxy SVG supports hex notation with alpha channel as well (https://t.co/o2OW1I19t9), but it uses the short notation when the alpha is 1 (e.g. #000 rather than #000000ff)
@NinaLimpi Is it not possible because of technical limitations (no API) or because of your business plan? I don't really need an API and I could show a big banner pointing to unDraw+ service together with the search results.