On Wed, Jan 2, 2013 at 11:21 PM, Steve Block wrote:
> - Would people welcome changes to encourage that policy?
FWIW, in Chromium (downstream, non-WebKit) we ended up adding a "vector"
(as in math, not the STL) class recently to address the sort of
"offset/delta between two points" use you're des
Hi webkit,
I was hoping that somebody could clarify the policy regarding the
correct use of Int/FloatPoint vs Int/FloatSize.
It seems that xxxPoint is consistently used to represent a position,
which makes sense. However, when representing the position of one
point relative to another, both xxxPo
Should be fixed. Let me know if you see problems.
On Wed, Jan 2, 2013 at 11:41 AM, Ojan Vafai wrote:
> If you expand diff context and then publish comments, the review tool
> might drop some of your comments. I'll have this fixed today. In the
> meantime, if you avoid expanding context or reloa
If you expand diff context and then publish comments, the review tool might
drop some of your comments. I'll have this fixed today. In the meantime, if
you avoid expanding context or reload the page before publishing, you
should avoid hitting this bug.
https://bugs.webkit.org/show_bug.cgi?id=10525
All,
There has been a proposal that a new property is added to the canvas 2D
drawing context called fillRule with values "nonzero" (default) and
"evenodd". This is compatible with the mozFillRule already implemented in
Mozilla Firefox and would be on track to become a web standard.
If you are in
Based on our discussion in September, the Chromium port has been
shipping for a while with webkitPostMessage compiled out. We've been
monitoring our support channels and haven't found any reports of
compatibility problems. (By way of comparison, we did find some
compatibility problems with removi
6 matches
Mail list logo
