[whatwg] Still beating the drawString() dead horse...

Stefan Haustein wrote:
> 
> Everything beyond is a separate use case that should be discussed 
> separately. I think the main problem here is that drawElement() was 
> suggested as a kind of replacement for drawString(), but it is actually 
> something completely different, that should be discussed separately. 

I agree. It would be nice to have both.

In the worst case, browsers can implement drawString in terms of 
drawElement if having both is a concern to developers.