- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Mon, 30 Mar 2009 10:23:52 -0500
- To: Brad Kemper <brad.kemper@gmail.com>
- Cc: Andrew Fedoniouk <news@terrainformatica.com>, David Hyatt <hyatt@apple.com>, Anne van Kesteren <annevk@opera.com>, Bert Bos <bert@w3.org>, "www-style@w3.org list" <www-style@w3.org>
On Mon, Mar 30, 2009 at 10:05 AM, Brad Kemper <brad.kemper@gmail.com> wrote: > > On Mar 30, 2009, at 5:01 AM, Tab Atkins Jr. wrote: > >> On Mon, Mar 30, 2009 at 2:08 AM, Brad Kemper <brad.kemper@gmail.com> >> wrote: >>> >>> On Mar 29, 2009, at 9:50 PM, Andrew Fedoniouk wrote: >>>> >>>> Sorry but border is not an outline either. E.g. outline does not >>>> participate in hits testing. But border does. How you border image >>>> solution will handle :hover state? >>> >>> Those are good questions. I suppose for simplicity anything outside the >>> border-box would not participate in hit testing or hover testing. >> >> This would also be a very good argument for still combining >> border-radius with border-image; border-radius will clip the hit box, >> which can be useful to match up with some border-image shapes. > > For hit-testing, yes. For clipping, no. If I have to chose between > hit-testing and not having my image clipped by the radius, then I prefer > the latter. Consider an images like these: > > http://www.bradclicks.com/cssplay/border-image/borders.png > > In each case, it would be useful to have border-radius for fallback, for > background-clipping, and for hit/hover-testing, but not for clipping the > border-image. Certainly; I did not mean to imply otherwise. It should have a layout effect, as it does now, but in and of itself be invisible, and have no effect on border-image (which already ignores all other layout concerns in your proposal). ~TJ
Received on Monday, 30 March 2009 15:24:28 UTC