Comments on: Box Shadow http://webkit.org/blog/86/box-shadow/ All about WebKit development Sat, 21 Nov 2009 23:00:28 -0800 http://wordpress.org/?v=2.8.5 hourly 1 By: Apples Safari nun auch fuer Windows - Tobbis Blog - Aktuelles über Windows, Opera & Co. gebloggt von Tobias Steinicke http://webkit.org/blog/86/box-shadow/comment-page-1/#comment-22325 Apples Safari nun auch fuer Windows - Tobbis Blog - Aktuelles über Windows, Opera & Co. gebloggt von Tobias Steinicke Tue, 12 Jun 2007 08:44:23 +0000 http://webkit.org/blog/?p=86#comment-22325 [...] unterstützt auch CSS-Eigenschaften wie text-shadow, box-shadow, mulitple backgrounds und Media Queries, einer Eigenschaft von [...] [...] unterstützt auch CSS-Eigenschaften wie text-shadow, box-shadow, mulitple backgrounds und Media Queries, einer Eigenschaft von [...]

]]> By: Thoughts from a Redesign | K-Squared Ramblings http://webkit.org/blog/86/box-shadow/comment-page-1/#comment-17839 Thoughts from a Redesign | K-Squared Ramblings Mon, 12 Feb 2007 07:14:48 +0000 http://webkit.org/blog/?p=86#comment-17839 [...] bkit (with any luck, the feature will be in the next version of Safari). Really neat was box-shadow, so far only in Webkit. I was finally able to add the drop-shadows to the article and sidebar the way I [...] [...] bkit (with any luck, the feature will be in the next version of Safari). Really neat was box-shadow, so far only in Webkit. I was finally able to add the drop-shadows to the article and sidebar the way I [...]

]]> By: richcon http://webkit.org/blog/86/box-shadow/comment-page-1/#comment-16840 richcon Sun, 14 Jan 2007 01:01:43 +0000 http://webkit.org/blog/?p=86#comment-16840 While fixing bugs is undeniably important, I for one am glad to see the WebKit team pushing ahead with support for future standards like CSS3 and other breakthrough-but-seldom-used standards like SVG. This work is critical to the future evolution of the Web, and to testing these standards and helping to ready them for prime time. And that, combined with Gecko's support, will (hopefully) help prod that other browser maker into supporting them as well. Bug fixing and adding new features are both important and need to be balanced, and as far as I can tell, the WebKit team is doing a great job at that. While fixing bugs is undeniably important, I for one am glad to see the WebKit team pushing ahead with support for future standards like CSS3 and other breakthrough-but-seldom-used standards like SVG. This work is critical to the future evolution of the Web, and to testing these standards and helping to ready them for prime time. And that, combined with Gecko’s support, will (hopefully) help prod that other browser maker into supporting them as well.

Bug fixing and adding new features are both important and need to be balanced, and as far as I can tell, the WebKit team is doing a great job at that.

]]> By: Andreas Amann http://webkit.org/blog/86/box-shadow/comment-page-1/#comment-16606 Andreas Amann Wed, 10 Jan 2007 19:30:09 +0000 http://webkit.org/blog/?p=86#comment-16606 After making a very reduced test case it seems as if the box-shadow indeed works correctly on a div - I guess I will have to figure out why it was not showing up when having the full page. Sorry for the confusion and I like the new property - it looks great! After making a very reduced test case it seems as if the box-shadow indeed works correctly on a div – I guess I will have to figure out why it was not showing up when having the full page.

Sorry for the confusion and I like the new property – it looks great!

]]> By: Michael(tm) Smith » WebKit devs kicking some CSS ass http://webkit.org/blog/86/box-shadow/comment-page-1/#comment-16582 Michael(tm) Smith » WebKit devs kicking some CSS ass Wed, 10 Jan 2007 11:27:32 +0000 http://webkit.org/blog/?p=86#comment-16582 [...] that is, for adding outline effects to character glyphs), followed by support for the CSS3 box-shadow property. Bonus feature: While you’re over at the Surfin’ Safari blog, make sure to also chec [...] [...] that is, for adding outline effects to character glyphs), followed by support for the CSS3 box-shadow property. Bonus feature: While you’re over at the Surfin’ Safari blog, make sure to also chec [...]

]]> By: Andreas Amann http://webkit.org/blog/86/box-shadow/comment-page-1/#comment-16573 Andreas Amann Wed, 10 Jan 2007 08:26:59 +0000 http://webkit.org/blog/?p=86#comment-16573 Darn - there should have been a <div> in the text above... Darn – there should have been a <div> in the text above…

]]> By: Andreas Amann http://webkit.org/blog/86/box-shadow/comment-page-1/#comment-16572 Andreas Amann Wed, 10 Jan 2007 08:25:11 +0000 http://webkit.org/blog/?p=86#comment-16572 I am not sure I understand "(3) It works on inline flows that span multiple lines." correctly - I tried to se t a shadow on a (which is used as a rollover popup on my Dashboard widget) using the latest nightly and it didn't give me any shadow... It would be great if it worked on block divs as well so that I don't have to resort to manually building a shadow using multiple divs around the content. I am not sure I understand “(3) It works on inline flows that span multiple lines.” correctly – I tried to se t a shadow on a (which is used as a rollover popup on my Dashboard widget) using the latest nightly and it didn’t give me any shadow…

It would be great if it worked on block divs as well so that I don’t have to resort to manually building a shadow using multiple divs around the content.

]]> By: daniel http://webkit.org/blog/86/box-shadow/comment-page-1/#comment-16526 daniel Tue, 09 Jan 2007 14:16:00 +0000 http://webkit.org/blog/?p=86#comment-16526 Everyone can see that you are working hard to make WebKit/Safari better every day by downloading the nightlies. Really! Correct me if I'm wrong but fixing bugs affects more pages than implementing features that are specific to WebKit. How many CSS-files contain these attributes that are unsupported by any other browser. Write about the bugs you fixed, too. It's important work! Personally I would love to read things like: "Bug #6790 is fixed, position:fixed works now." Or even better: "This week was our internal 'Week of CSS Bugs': We resolved all 52 bugs that have CSS in the title. (And also Bug 6790)" Everyone can see that you are working hard to make WebKit/Safari better every day by downloading the nightlies. Really! Correct me if I’m wrong but fixing bugs affects more pages than implementing features that are specific to WebKit. How many CSS-files contain these attributes that are unsupported by any other browser.

Write about the bugs you fixed, too. It’s important work!

Personally I would love to read things like: “Bug #6790 is fixed, position:fixed works now.”

Or even better: “This week was our internal ‘Week of CSS Bugs’: We resolved all 52 bugs that have CSS in the title. (And also Bug 6790)”

]]> By: hyatt http://webkit.org/blog/86/box-shadow/comment-page-1/#comment-16515 hyatt Tue, 09 Jan 2007 09:56:00 +0000 http://webkit.org/blog/?p=86#comment-16515 We are working very hard on compatibility always. I did box-shadow by myself in a handful of hours. In this case it was trivial to add because CG provides the shadow drawing support, and the parsing of the property is identical to text-shadow. This made it quite easy to just blast it out quickly. When features like this land in the tree, it does not mean compatibility work is "not getting done." I blog about these sorts of features because I like to think they are interesting. If you'd rather I sit around blogging about our compatbility fixes, I could do that, but I think it would make for a boring blog. :) "Today I fixed a bug where table cells incorrectly expanded to encompass floats inside an overflow:auto block with a fixed height." Zzzzz. There are many many people working very hard every day on compatibility. Browsing the cited quirksmode.org page of Safari bugs with a nightly, you will notice that many of the issues have in fact been fixed. We are working very hard on compatibility always. I did box-shadow by myself in a handful of hours. In this case it was trivial to add because CG provides the shadow drawing support, and the parsing of the property is identical to text-shadow. This made it quite easy to just blast it out quickly.

When features like this land in the tree, it does not mean compatibility work is “not getting done.” I blog about these sorts of features because I like to think they are interesting. If you’d rather I sit around blogging about our compatbility fixes, I could do that, but I think it would make for a boring blog. :)

“Today I fixed a bug where table cells incorrectly expanded to encompass floats inside an overflow:auto block with a fixed height.” Zzzzz.

There are many many people working very hard every day on compatibility. Browsing the cited quirksmode.org page of Safari bugs with a nightly, you will notice that many of the issues have in fact been fixed.

]]> By: sjakelien http://webkit.org/blog/86/box-shadow/comment-page-1/#comment-16505 sjakelien Tue, 09 Jan 2007 09:12:52 +0000 http://webkit.org/blog/?p=86#comment-16505 With all due respect, and indeed, it's due, the following: Since this web site is 'powered by WordPress', you WebKit guys should have noticed that the text editing experience in WordPress is not as rich if you use Safari, compared to FireFox and (god forbid) IE. Being a software developer, it's kind of embarassing that in some cases, I cannot support Safari, because I have to offer my customers web-based functionality that is not available through Safari. What I want to say is: I like the very strict, almost puritan approach of adhering to standards, but the current efforts in offering CSS3 functionality (which, as pointed out, is not even close to being a standard) could be better directed towards ensuring compatibility with de facto standards like WordPress, or TinyMCE . Sorry for the interruption. With all due respect, and indeed, it’s due, the following:
Since this web site is ‘powered by WordPress’, you WebKit guys should have noticed that the text editing experience in WordPress is not as rich if you use Safari, compared to FireFox and (god forbid) IE.
Being a software developer, it’s kind of embarassing that in some cases, I cannot support Safari, because I have to offer my customers web-based functionality that is not available through Safari.
What I want to say is: I like the very strict, almost puritan approach of adhering to standards, but the current efforts in offering CSS3 functionality (which, as pointed out, is not even close to being a standard) could be better directed towards ensuring compatibility with de facto standards like WordPress, or TinyMCE .
Sorry for the interruption.

]]>