Hi, blink-dev, As the second part of crbug.com/738465, we have finished migrating blink to use gfx int/float geometry types:
- blink::IntRect -> gfx::Rect - blink::IntPoint -> gfx::Point (if it's a point) or gfx::Vector2d (if it's an offset) - blink::IntSize -> gfx::Size (if it's a size) or gfx::Vector2d (if it's an offset) - blink::FloatRect -> gfx::RectF - blink::FloatPoint -> gfx::PointF (if it's a point) or gfx::Vector2dF (if it's an offset) - blink::FloatSize -> gfx::SizeF (if it's a size) or gfx::Vector2dF (if it's an offset) - blink::FloatBox -> gfx::BoxF - blink::FloatQuad -> gfx::QuadF - blink::FloatPoint3D -> gfx::Point3F (if it's a point) or gfx::Vector3dF (if it's an offset) - blink::IntRectOutsets -> gfx::Outsets or gfx::Insets - blink::FloatRectOusets -> gfx::OutsetsF or gfx::Outsets Most differences between the blink types and gfx types are straightforward, but the following are notable: - gfx::Size, gfx::SizeF, gfx::Rect and gfx::RectF clamp negative width/height to zero. - All gfx integer geometry types clamp values to integer range. Some stored values are clamped to prevent overflow of calculated values. For example, gfx::Rect clamps also clamps width to prevent overflow of right (x+width). Cheers, Xianzhu -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADBxricqKD4J%2Bvm_d8bpcD9QX6Ux-3qSctX_YHN-bPU9Fc-zxw%40mail.gmail.com.
