Consider merging https://chromium.googlesource.com/chromium/blink/+/873dbff72d843c6e6828e48087a76d5fbd30d4a3 if we want to support object-position CSS property This is hidden behind an "experimental" runtime flag named "ObjectFitPosition", together with object-fit. This is an implementation of object-position as described in http://www.w3.org/TR/2012/CR-css3-images-20120417/#object-position Object-position is used to offset replaced content within its content box. Painting is always clipped against the content box, regardless of the "overflow" property. This property is useful together with object-fit (to achieve a difference between content box size and replaced content size, so that specifying alignment is interesting), but can also be used on its own.
Reverted in https://chromium.googlesource.com/chromium/blink/+/e76e70050d8f8d9cacd99c20d3b4a1ae51becf60
Relanded in https://chromium.googlesource.com/chromium/blink/+/b137387c4adbe19621da8d46a6642ae94d8affe0
<rdar://problem/15836338>
Please fix this problem as soon as possible. Chrome 31 and Firefox 36 has supported. https://developer.mozilla.org/zh-CN/docs/Web/CSS/object-position#Browser_compatibility
Also hoping for implementation. I've filed a bug with Apple Bug reporter as occurring in Safari - their issue/filing number 23777385. Awaiting pickup. Happy to help if anything can be done currently.
Ok, my Apple Bug Reporter issue #23777385 response is that the issue is a duplicate of an exising open issue #15836338. Mine has therefore been closed. Apple Bug Reporter doesn't disclose any further information on the open issue #15836338 to me as I didn't file it, only that it exists and is open. Optimistically it's been +1ed and progress on resolution is well on its way. In reality, who knows unless you work there fixing bugs. Fingers crossed then I suppose! I would welcome hearing from anyone who knows more on this issue...
(In reply to comment #6) > Ok, my Apple Bug Reporter issue #23777385 response is that the issue is a > duplicate of an exising open issue #15836338. Mine has therefore been closed. > > Apple Bug Reporter doesn't disclose any further information on the open > issue #15836338 to me as I didn't file it, only that it exists and is open. > > Optimistically it's been +1ed and progress on resolution is well on its way. > In reality, who knows unless you work there fixing bugs. Fingers crossed > then I suppose! > > I would welcome hearing from anyone who knows more on this issue... I think Simon Fraser(simon.fraser@apple.com) can help us fix this bug.
Created attachment 273103 [details] Patch
https://trac.webkit.org/r197618
Could you please correct iOS results? There are three new failures. https://build.webkit.org/results/Apple%20iOS%209%20Simulator%20Release%20WK2%20(Tests)/r197618%20(3676)/results.html
(In reply to comment #10) > Could you please correct iOS results? There are three new failures. > > https://build.webkit.org/results/ > Apple%20iOS%209%20Simulator%20Release%20WK2%20(Tests)/r197618%20(3676)/ > results.html Filed https://bugs.webkit.org/show_bug.cgi?id=155116 to track.