<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugs.webkit.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4.1"
          urlbase="https://bugs.webkit.org/"
          
          maintainer="admin@webkit.org"
>

    <bug>
          <bug_id>162604</bug_id>
          
          <creation_ts>2016-09-27 04:42:40 -0700</creation_ts>
          <short_desc>WebGL: drawingBuffer problems with Ultra HD Resolutions</short_desc>
          <delta_ts>2017-10-18 10:15:38 -0700</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>WebKit</product>
          <component>WebGL</component>
          <version>Safari 10</version>
          <rep_platform>Mac</rep_platform>
          <op_sys>OS X 10.11</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>DUPLICATE</resolution>
          <dup_id>178223</dup_id>
          <see_also>https://bugs.chromium.org/p/chromium/issues/detail?id=445542</see_also>
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords>BlinkMergeCandidate, EasyFix, InRadar, WebExposed</keywords>
          <priority>P2</priority>
          <bug_severity>Normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Michael Herzog">michael.herzog</reporter>
          <assigned_to name="Nobody">webkit-unassigned</assigned_to>
          <cc>dino</cc>
    
    <cc>simon.fraser</cc>
          

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>1233812</commentid>
    <comment_count>0</comment_count>
    <who name="Michael Herzog">michael.herzog</who>
    <bug_when>2016-09-27 04:42:40 -0700</bug_when>
    <thetext>Steps to reproduce the problem:

1. First you need a high resolution monitor (e.g. iMac 5K)
2. Start Safari and maximize your window
3. Go to http://threejs.org/examples/webgl_interactive_cubes.html

What is the expected behavior?

When you position your mouse exactly over a cube, it should be highlighted.

What went wrong?

On ultrad HD resolutions the application is not able to determine the correct cube. This problem only occurs when Safari exceeds a specific resolution. On smaller monitors (e.g.FullHD), everything works fine.

Did this work before? 

No 

Details:

I assume that Webkit must be limiting the maximum drawing buffer width/height which leads to incorrect canvas sizes.

My recommendation is to change the backbuffer limit from e.g. 4k per dimension to 4k x 4k total area like Blink does (see https://bugs.chromium.org/p/chromium/issues/detail?id=445542)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1264523</commentid>
    <comment_count>1</comment_count>
    <who name="Simon Fraser (smfr)">simon.fraser</who>
    <bug_when>2017-01-06 14:50:46 -0800</bug_when>
    <thetext>rdar://problem/25511381</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1360562</commentid>
    <comment_count>2</comment_count>
    <who name="Michael Herzog">michael.herzog</who>
    <bug_when>2017-10-15 04:40:36 -0700</bug_when>
    <thetext>This problem is becoming increasingly critical as more users have high-resolution displays. Without any workarounds, interactive 3D applications like the mentioned three.js demo are unusable in combination with a large canvas.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1361373</commentid>
    <comment_count>3</comment_count>
    <who name="Simon Fraser (smfr)">simon.fraser</who>
    <bug_when>2017-10-17 13:00:46 -0700</bug_when>
    <thetext>Dup of bug 178223?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1361758</commentid>
    <comment_count>4</comment_count>
    <who name="Michael Herzog">michael.herzog</who>
    <bug_when>2017-10-18 10:15:38 -0700</bug_when>
    <thetext>Yes. Although your mentioned bug is far newer than this post. 

Also consider the fix of Blink (https://bugs.chromium.org/p/chromium/issues/detail?id=445542).

*** This bug has been marked as a duplicate of bug 178223 ***</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>