No graphics shown in some of the canvas demo website.

NEW
Unassigned

Status

()

Core
Graphics
P3
normal
5 months ago
4 months ago

People

(Reporter: Roshan Dawande, Unassigned)

Tracking

52 Branch
x86_64
Windows 10
Points:
---

Firefox Tracking Flags

(firefox51 affected)

Details

(Whiteboard: [gfx-noted])

Attachments

(5 attachments)

(Reporter)

Description

5 months ago
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

Steps to reproduce:

Step 1- Launch Firefox.	
Step 2-Goto  https://developer.mozilla.org/en-US/docs/Web/Demos_of_open_web_technologies	
Step 3- Click on Blob's demos
            Click on MSX Emulator
            Click on 3D on 2D Canvas


Actual results:

No Graphics displayed.


Expected results:

some graphics should be displayed.
(Reporter)

Updated

5 months ago
OS: Unspecified → Windows 10
Hardware: Unspecified → x86_64

Comment 1

5 months ago
Can you attch screenshot for the link http://gyu.que.jp/jscloth/ (3D on 2D Canvas)?
Flags: needinfo?(rdroshan28)
(Reporter)

Comment 2

5 months ago
Created attachment 8829754 [details]
screenshot1.jpg
Flags: needinfo?(rdroshan28)
(Reporter)

Comment 3

5 months ago
No graphics are shown in any of the case.
And in demo3, When i click "opera 3D or Gecko 3D" "This browser does not support any 3D canvas" message shows.
(Reporter)

Updated

5 months ago
Component: Untriaged → Developer Tools: Canvas Debugger
(Reporter)

Updated

5 months ago
Component: Developer Tools: Canvas Debugger → Untriaged

Comment 4

5 months ago
Hi Roshan,

I can see graphics using the link provided in comment 1. Could you please attach your "about:support" information? Thanks

Environment:
Version 	54.0a1
Build ID 	20170124030205
Update Channel 	nightly
User Agent 	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:54.0) Gecko/20100101 Firefox/54.0
Flags: needinfo?(rdroshan28)
(Reporter)

Comment 5

5 months ago
Created attachment 8832075 [details]
Page-Shot-2017-1-31 Troubleshooting Information.png
Flags: needinfo?(rdroshan28)

Comment 6

5 months ago
Created attachment 8833098 [details]
mozregression for windows Instruction.txt

Roshan,

I have added the extensions on aurora 52.0a1 based on the information provided in comment 5. I have with windows 10 64bits with NVIDIA GeForce GTX 745 graphics, unlike yours (intel HD).  So I could not manage to reproduce it.

Could you provide a regression range using the mozregression tool if it is a regression issue? 
I have attached installation and usage information about the tool.

Thanks
Flags: needinfo?(rdroshan28)

Comment 7

5 months ago
Tested on latest nightly and aurora 52.0a2
--
Version 	52.0a2
Build ID 	20170122004006
Update Channel 	aurora
User Agent 	Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0
(Reporter)

Comment 8

5 months ago
Created attachment 8833262 [details]
mozregression.JPG

I was able to reproduce this issue in Firefox Nightly also.
I didn't understood the steps to produce range from mozregression, Still i have tried.
Please check.
Flags: needinfo?(rdroshan28)

Comment 9

5 months ago
Mozregression failed because you entered 2016-12-10 was a good build for left boundary then you replied it was a bad build when the tool checked this build.

If 2016-12-10 is bad, just enlarge to older builds, like --good=51 or 50 (if you're sure FF50/51 are working fine).

Updated

5 months ago
status-firefox51: --- → affected

Comment 10

5 months ago
Created attachment 8833342 [details]
testcase.png

Comment 11

5 months ago
[testday-20170203]
OPERATING SYSTEM : Windows10.0
BROWSER : Firefox Beta 51.0
Status: UNCONFIRMED → NEW
Ever confirmed: true

Updated

4 months ago
Component: Untriaged → Graphics
Product: Firefox → Core

Updated

4 months ago
Has STR: --- → yes
Priority: -- → P3
Whiteboard: [gfx-noted]
(Reporter)

Comment 12

4 months ago
Not able to understand mozregression. Please provide a indepth description of the steps involved.
Flags: needinfo?(epinal99-bugzilla2)
Flags: needinfo?(amasresha)

Comment 13

4 months ago
(In reply to Roshan Dawande from comment #12)
> Not able to understand mozregression. Please provide a indepth description
> of the steps involved.

When you run mozregression, you need to enter a valid interval for nightly builds, e.g. [good-bad] or more simply [good[.

In your case the build you thought good (2016-12-10) was in fact bad, so mozregression aborted.
Just reduce the date for good build, like good=51 or 50 (mozreg accepts release number), and try again. You don't need to specify a bad build, just "mozregression --good=XXX".
Flags: needinfo?(epinal99-bugzilla2)

Comment 14

4 months ago
Could you try "mozregression --good=XX --bits=32" where xx is a known good build? Example, if 51 is a good build, then run "mozregression --good=51 --bits=32".
Thanks

Updated

4 months ago
Flags: needinfo?(amasresha)
You need to log in before you can comment on or make changes to this bug.