Subscribe: Comments on: CSS Canvas Drawing
http://webkit.org/blog/176/css-canvas-drawing/feed/
Added By: Feedage Forager Feedage Grade B rated
Language: English
Tags:
canvas  css  expect work  feature  features  hyatt  maciej stachowiak  make  mathml  proposed standard  standard  web  webkit  work webkit  work 
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: Comments on: CSS Canvas Drawing

Comments on: CSS Canvas Drawing



Open Source Web Browser Engine



Last Build Date: Thu, 01 Mar 2012 22:03:34 +0000

 



By: Dethe Elza

Mon, 05 May 2008 17:05:52 +0000

If Canvas and SVG can be expected to work where CSS expects an image, can I expect that to work with -webkit-border-image as well? I am trying this with SVG content in the nightly Webkit (circa 2006-04-04) and not seeing a result. Trying to figure out if I'm doing something wrong, or this isn't something I should expect to work.



By: Dave Hyatt

Fri, 25 Apr 2008 22:11:15 +0000

Robert, ultimately yes. There is no way to achieve that in WebKit today though since XBL doesn't exist yet.



By: Robert O'Callahan

Fri, 25 Apr 2008 07:37:13 +0000

Dave, so you consider the scripts that populate the canvas(es) as *not* part of the content?



By: Maciej Stachowiak

Sun, 20 Apr 2008 22:46:57 +0000

I don't know if Hyatt would agree, but if this functionality turns out to be useful, I do think we should propose it as a standard. Right now I think it's too experimental to really know where it's going.



By: dazzaj

Sun, 20 Apr 2008 22:05:46 +0000

@simx. Read the Project Goals detailed on this site. The first goal should make it clear why some features that are added to Webkit will not be proposed as a standard. Webkit is used in many contexts besides a standards compliant web browser and so some non standard features are required to support that.



By: simx

Sun, 20 Apr 2008 19:17:54 +0000

What's the rationale behind not proposing it as a standard, besides not knowing to whom to propose it? Why would we want a potentially useful feature like this if it isn't going to be used by other browsers? It seems like all the web functionality in WebKit that's not already a standard or proposed as a standard should be, otherwise it shouldn't be in WebKit.



By: Maciej Stachowiak

Sun, 20 Apr 2008 07:32:28 +0000

@ctachme, @KarlWa WebKit is not a centrally planned project. We don't decree, "these are the new features WebKit hackers will work on, and nothing else". For one thing, many of our contributors are volunteers. For another, even people like Hyatt who are paid by big companies to work on WebKit, are encouraged to pursue cool new stuff. We like to keep a good balance of fun, innovative things, and more straightforward improvements. So if there's particular features you want, please file requests, or comment in the particular bugs. But it doesn't make sense to say "you should do my favorite feature X instead of this other feature Y". Don't make it an either-or, just ask for the things you actually want, and you will find we are pretty responsive to web developer requests.



By: David Smith

Sat, 19 Apr 2008 20:15:16 +0000

Actually CSS Gradients is (or will be shortly) proposed as a standard, thanks for playing though! (Also what makes you think Hyatt is even the right person to implement MathML? People *do* have areas they specialize in, you know)



By: KarlWa

Sat, 19 Apr 2008 15:54:27 +0000

You could be doing more useful things - like implementing MathML. CSS Gradients and Canvas Drawings are great, but they're not standards, so they won't see much use. MathML is a standard, and is already used widely.



By: jeffr

Fri, 18 Apr 2008 19:15:20 +0000

ctachme, keep in mind that WebKit is not just used in Safari. It is also used heavily in technologies such as Mac OS X's Dashboard, all over the iPhone, and tons of other specific places. Even though a feature may not be useful to the general browser market, I could definitely see how a feature like this would still be very important to a ton of developers.