On Mar 29, 2009, at 2:40 AM, Brad Kemper wrote:
> On Mar 28, 2009, at 7:54 AM, David Hyatt wrote:
>
>> On Mar 28, 2009, at 8:17 AM, Anne van Kesteren wrote:
>>
>>> On Fri, 27 Mar 2009 17:58:52 +0100, David Hyatt <hyatt@apple.com>
>>> wrote:
>>>> Yeah, I guess I'm saying "let's just drop the ability to set
>>>> border widths from border-image."
>>>
>>> Then you always have to set two properties. Is it worth
>>> considering making border-image a special form of border-style?
>>> That does not work for the border-*-style properties, but the same
>>> applies to resetting border-image by setting border. As a bonus it
>>> would make it easier to allow specifying some kind of fallback in
>>> case the image fails to load, cannot be decoded, is not supported,
>>> etc.
>>>
>>
>> I don't really care how this is solved. I just don't like what's
>> in the spec now, since snapping to different border widths just
>> because an image failed to load does not seem like what any author
>> or user would want.
>>
>> dave
>
> I written up a proposal that I think solves this problem, plus a
> couple others that I think are even bigger for authors. I'd
> appreciate it if everyone could take a look and let me know what you
> think. In the following link, I describe three problems (including
> this one), and a nice solution that I would love to see implemented:
>
> http://www.bradclicks.com/cssplay/border-image/Thinking_Outside_The_Box.html
>
>
I think this proposal is fantastic. I would love to see it
incorporated into the spec.
dave
(hyatt@apple.com)