New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 612680 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: May 2016
Cc:
█ ranjitkan@chromium.org
vmp...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

background transparency not working in print preview when combined with box-shadow

Reported by roberto....@agila.com.br, May 18 2016 
Chrome Version: 
Google Chrome	50.0.2661.102 (Versão oficial) m 32 bits
Revisão	c26c0312e940221c424c2730ef72be2c69ac1b67-refs/branch-heads/2661@{#680}
SO	Windows 
Blink	537.36 (@c26c0312e940221c424c2730ef72be2c69ac1b67)
JavaScript	V8 5.0.71.48
Flash	21.0.0.242


Other browsers tested: none (worked on previus chrome version)

What steps will reproduce the problem:
Run the HTML:

<html>
<head>
	<style type="text/css">
		.clrs01 {
			width: 80mm; height: 70mm;
			background-color: rgba(68, 187, 255, 0.8);
		}
		.pmc-el-content {
			width: 50mm;  height: 100mm;
			background: rgba(255, 255, 204, 0.7);
			box-shadow: 2px 2px 4px rgba(33,33,33,.7);
		}
	</style>
</head>
<body>
	<div class="clrs01">
		<div class="pmc-el-content">
		</div>  				
	</div>
</body>
</html>

Use 'Ctrl + P' to open print preview window.


What is the expected result?
The transparency effect of div with class "pmc-el-content" will work as expected (as a transparency).

What happens instead?
The div is shown opaque.
bug_reproduce.html
414 bytes View Download
bug_print.png
9.6 KB View Download

Comment 1 by ssamanoori@chromium.org, May 19 2016

Components: UI>Browser>PrintPreview
Labels: Needs-Feedback
Tested the issue on Windows 7, Mac 10.11.5, Ubuntu 14.04 using 50.0.2661.102 (m 32 bit, m 64 bit), latest canary 52.0.2740.0 with below steps:

1.Opened bug_reproduce.html in chrome.
2.Hit ctrl+p to get print preview.
3.Observed the preview screen as in attached screenshot.

Please find attached screenshot and confirm if this is the issue.

roberto.barra@Could you please provide expected behavior screenshot for better understanding the issue to triage it further.
612680.png
111 KB View Download

Comment 2 by thestig@chromium.org, May 19 2016

Components: Blink>CSS

Comment 3 by roberto....@agila.com.br, May 19 2016 

Hi!

The expected behaviour it would be the same transparency effect as observed on Chrome 'regular' view.

The image that I uploaded together with the sample code to reproduce the error has the two screenshots combined: at the left side, the expected result (screenshot from Chrome rendering the HTML). At the right side, the problematic result (screenshot from the print preview viewport).

I think that the result that you uploaded has some print optimization turned on (checked to do not show background images / patterns).

I'm uploading a full screnshot from de print preview window. I hope it helps!

Regards,
print_preview_full_screenshot.png
47.2 KB View Download

Comment 4 by timloh@chromium.org, May 19 2016

Components: -Blink>CSS Blink>Paint
Sounds like a paint issue.

Comment 5 by timloh@chromium.org, May 19 2016

Labels: -Needs-Feedback
Status: Untriaged (was: Unconfirmed)

Comment 6 by timloh@chromium.org, May 19 2016

Status: Unconfirmed (was: Untriaged)
Actually, going to leave this as unconfirmed for paint team to look into. Repros for me on M50 crOS but doesn't repro on M52/Linux or ToT/Linux

Comment 7 by ranjitkan@chromium.org, May 26 2016

Cc: ranjitkan@chromium.org
Labels: Needs-Feedback
Thanks for the details provided, able to reproduce the issue on chrome version 50.0.2661.102, but issue is fixed on current stable 51.0.2704.63. Attached screen shot for the same.

@ roberto.barra: Request you to please try the same on the latest stable available and update us with your observations.

Thanks.!
Print_Preview.png
36.6 KB View Download

Comment 8 by roberto....@agila.com.br, May 27 2016 

Tested on version 51.0.2704.63, and the bug is fixed!

Thanks a lot!

Comment 9 by ranjitkan@chromium.org, May 27 2016

Labels: -Needs-Feedback
Status: WontFix (was: Unconfirmed)
Thanks for the update, closing the issue as per above comment.
►

Sign in to add a comment