dave-buzzy

@webprofusion-chrisc @WillyRamirez Did this ever get addressed? Am seeing the same thing, and can't use the generated images because of this.

@webprofusion-chrisc just tried it in the pica demo. Leaving their default settings untouched, the artefact still shows up. I can remove it by either decreasing the `unsharp amount` setting to...

@webprofusion-chrisc Yep, looks like your values (`unsharpAmount: 80, unsharpRadius: 0.6, unsharpThreshold: 2,`) are what pica has on their demo and docs as recommended default starting points. Guess it's a use-case...

@DanDeMicco @adamgins There's a whole bunch of very generic classnames in the Box css (as downloaded from eg https://cdn01.boxcdn.net/platform/elements/6.0.0/en-US/picker.css) that aren't prefixed - `.btn-, .toggle, .menu-toggle, .radio-, .select-option` and more...

@DanDeMicco @adamgins Ok, so the quarantining of the Box styles and unprefixed classes via css-specificity kinda works for the main UI. However, the box UI uses a bunch of elements...

~Actually, another hack would be if we could pass Box a 'parent' parameter which specifies where in the dom dynamic elements should be written - eg `` appears to be...

Cool, thanks @DanDeMicco - thought it was something like that; we were/are in a rush on this, so the quarantining hack above was my best option of a workaround without...