20454 2008-08-19 16:20:25 -0700 getPropertyValue() for clip returns wrong value 2022-07-27 17:57:38 -0700 1 1 1 Unclassified WebKit CSS 528+ (Nightly build) All All RESOLVED CONFIGURATION CHANGED InRadar P2 Normal --- 1 xk1t webkit-unassigned ahmad.saleem792 ap bdakin bfulgham jeffery.to michael.c.petrovich rniwa simon.fraser syoichi tabatkins zalan oldest_to_newest 88861 0 xk1t 2008-08-19 16:20:25 -0700 When reading clip value using getComputedValue, the wrong value is returned. The clip value should be returned, but instead, if the element is not clipped, all 0's are returned. See also: Bug 17433 88862 1 22884 xk1t 2008-08-19 16:20:51 -0700 Created attachment 22884 Testcase showing problem 88866 2 mrowe 2008-08-19 16:28:52 -0700 <rdar://problem/6160816> 441583 3 jeffery.to 2011-07-25 01:10:01 -0700 Can someone have a look at this bug? As it stands, it is impossible to tell (from JavaScript) whether an element is visible or completely clipped. Currently, when an element has no "clip" CSS declaration, getComputedStyle correctly returns "auto". ("auto" meaning the element is not clipped) But when an element has "clip: auto" or "clip: rect(auto, auto, auto, auto)", getComputedStyle returns "rect(0px 0px 0px 0px)". This is a valid clip value, but this value means the element is completely clipped. 442068 4 jeffery.to 2011-07-25 19:12:50 -0700 In other words, when I get "rect(0px 0px 0px 0px)" from getComputedStyle, I can't tell if the clip value is actually "auto" and the element is visible, or if the clip value is "rect(0px 0px 0px 0px)" and the element is completely clipped. 442098 5 xk1t 2011-07-25 21:24:53 -0700 (In reply to comment #4) > In other words, when I get "rect(0px 0px 0px 0px)" from getComputedStyle, I can't tell if the clip value is actually "auto" and the element is visible, or if the clip value is "rect(0px 0px 0px 0px)" and the element is completely clipped. That was what they called a "fix" for bug 17433. See bug 17433 comment 2. The problem is demonstrated in this bug, to attachment 22884. What Gecko does is to return "auto" which is different than a rect value, but the CSS 2.1 spec specifies a rect value. This makes sense and fortunately now too does CSS 2.1, which standardizes this behavior. | Computed value: 'auto' if specified as 'auto', | otherwise a rectangle with four values, each of | which is 'auto' if specified as 'auto' and the | computed length otherwise 442102 6 xk1t 2011-07-25 21:28:00 -0700 (In reply to comment #5) > (In reply to comment #4) > > In other words, when I get "rect(0px 0px 0px 0px)" from getComputedStyle, I can't tell if the clip value is actually "auto" and the element is visible, or if the clip value is "rect(0px 0px 0px 0px)" and the element is completely clipped. > > That was what they called a "fix" for bug 17433. See bug 17433 comment 2. The problem is demonstrated in this bug, to attachment 22884 [details]. > > What Gecko does is to return "auto" which is different than a rect value, but the CSS 2.1 spec specifies a rect value. Correction: previous version of CSS 2.1 specified that clip computed style must be a rect. The current version of CSS 2.1 matches what Gecko does and returns "auto" when clip is "auto". Again: > > | Computed value: 'auto' if specified as 'auto', > | otherwise a rectangle with four values, each of > | which is 'auto' if specified as 'auto' and the > | computed length otherwise 797299 7 michael.c.petrovich 2012-12-26 06:41:05 -0800 We're rewriting a lot of core effects in jQuery UI to use the CSS clip property, and being able to differentiate between "clip: rect(auto, auto, auto, auto)" and "clip: rect(0px, 0px, 0px, 0px)" is needed for a complete and correct implementation with Webkit browsers. Has there been any progress towards a resolution or workaround for this issue? 1887092 8 ahmad.saleem792 2022-07-27 10:08:44 -0700 I am unable to reproduce this bug using attached test case in Safari 15.6 on macOS 12.5 and it shows "green background" on text with blue border and I zoomed into find any clipping but I was not able to find. Also it matches with other browsers (Chrome Canary 106 and Firefox Nightly 105). I think this can be marked as "RESOLVED CONFIGURATION CHANGED". Thanks! 22884 2008-08-19 16:20:51 -0700 2008-08-19 16:20:51 -0700 Testcase showing problem clip2.html text/html 901 xk1t PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMDEgVHJhbnNpdGlvbmFs Ly9FTiIKICAgICAgICAiaHR0cDovL3d3dy53My5vcmcvVFIvaHRtbDQvbG9vc2UuZHRkIj4KPGh0 bWwgbGFuZz0iZW4iPgo8aGVhZD4KCTx0aXRsZT5jbGlwIHN0aWxsIGJyb2tlbjwvdGl0bGU+Cjwv aGVhZD4KPGJvZHk+CjxkaXYgc3R5bGU9J3Bvc2l0aW9uOiBhYnNvbHV0ZTsgYmFja2dyb3VuZDog IzNmMzsgYm9yZGVyOiAzcHggc29saWQgIzAwOTsgcGFkZGluZzogNHB4Jz4KCVRoaXMgZGl2IHNo b3VsZCBoYXZlIGEgZ3JlZW4gYmFja2dyb3VuZCB3aXRoIGEgYmx1ZSBib3JkZXIgb24gCglhbGwg Zm91ciBzaWRlcy4gTm8gY2xpcHBpbmcgc2hvdWxkIGJlIGFwcGFyZW50Lgo8L2Rpdj4KCjxwIGlk PSdmYWlsJyBzdHlsZT0iZGlzcGxheTpub25lOyBiYWNrZ3JvdW5kOiAjRjAwOyBtYXJnaW46IDJl bSI+RkFJTDwvcD4KCjxzY3JpcHQgdHlwZT0idGV4dC9qYXZhc2NyaXB0Ij4KZG9jdW1lbnQuYm9k eS5zdHlsZS5jbGlwID0gJ2F1dG8nOwoKLy8gVGhpcyBjb3VsZCBiZSBlYXNpZXIgaWYgZWxlbWVu dC5jb21wdXRlZFN0eWxlIHdlcmUgaW1wbGVtZW50ZWQuCnZhciBib2R5Q29tcHV0ZWRTdHlsZSA9 IGRvY3VtZW50LmRlZmF1bHRWaWV3LmdldENvbXB1dGVkU3R5bGUoZG9jdW1lbnQuYm9keSwgJycp Owp2YXIgY2xpcCA9IGJvZHlDb21wdXRlZFN0eWxlLmdldFByb3BlcnR5VmFsdWUoJ2NsaXAnKTsK CmlmKC8wLy50ZXN0KGNsaXApKSB7Cgl2YXIgZiA9IGRvY3VtZW50LmdldEVsZW1lbnRCeUlkKCdm YWlsJyk7CglmLnN0eWxlLmRpc3BsYXk9J2lubGluZS1ibG9jayc7CglmLmZpcnN0Q2hpbGQuZGF0 YSArPSAiOiAiICsgY2xpcDsKfQo8L3NjcmlwdD4KPC9ib2R5Pgo8L2h0bWw+Cg==