kpdecker / border-image-generator Goto Github PK

Having values of (40, 0, 0, 0) creates output like the following:

border-width: 40px;
-moz-border-image: url(firediff_small.PNG) 40;
-webkit-border-image: url(firediff_small.PNG) 40;
border-image: url(firediff_small.PNG) 40;

https://twitter.com/#!/thechosenrick/statuses/149684132069376001

"Can u add #imageEl{image-rendering:-moz-crisp-edges;} ?"

Should look into this on both moz and webkit.

http://github.com/lrbabe/borderimage/ allows for border-image functionality in some otherwise non-supporting browsers. We should provide the option to output the call necessary to use this API.

Any ideas for IE9 Support

Need to double check opera support.

Reports are that most features are working but the visual editor has some issues.

The output CSS should be optimized when possible by removing duplicate values (I.e. border-width: 4px; vs. border-width: 4px 4px 4px 4px;)

We need to allow changing the text color as some images will make this text difficult to read.

It appears that the vertical and horizontal repeat options are reversed.

file:// URLs appear to be failing due to security restrictions. Need to find some way to allow usage of images stored locally.

We should add methods to support setting border-image-repeat and platform specific implementations.

Since there are differences between the platform specific and standard implementations here, we should provide some hints as to what to expect on other platforms and spec differences.

Allow output of CSS for wrapper divs (for negative margins) if the dev wants to do this.

Pressing [toggle style] changes background color but after reloading the page it always returns to black.

I refer to border-image.com in my article "CSS, Retina, and Physical Pixels". The image I use is mostly black with transparent background:

It is hard to see it on dark background.

Need to handle support for border-image as defined by the spec and impl in later browsers.

http://blog.assortedgarbage.com/2011/12/change-happens/

Might run into concerns here when trying to support both new and old implementations. Perhaps could use canvas manipulation to create assets that have the specified behavior on the older browsers.

Need to do this for usability.