Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invisible eventless area around all sides of window #4749

Closed
gorelics opened this issue Apr 20, 2016 · 4 comments
Closed

Invisible eventless area around all sides of window #4749

gorelics opened this issue Apr 20, 2016 · 4 comments
Assignees
Milestone

Comments

@gorelics
Copy link

invis_clip_area

Hi, have a problem, invisible eventless area around all sides. html and body padding and margin 0px.
OS Windows 7 x64, nwjs-sdk-v0.14.0-win-x64

@rdtsc
Copy link

rdtsc commented Apr 20, 2016

Confirming this as well. Reproducible with the latest x64 build on Windows 7 and 10 only if DWM is running in non-basic/classic mode. GPU acceleration doesn't seem to make a difference.

Test case:

git clone https://gist.github.com/rdtsc/4ad3502f1835dbdfa66253e7775eb19f nwjs-4749

package.json:

{
  "name": "nwjs",
  "main": "index.html"
}

index.html:

<!doctype html>
<html lang="en">
  <head>
    <meta charset="utf-8">
    <title>NW.js</title>
    <style>
      html, body {
        margin: 0;
        padding: 0;
        height: 100%;
      }
      button {
        cursor: pointer;
        width: 100%;
        height: 100%;
      }
      button:active {
        background: #AAA;
      }
      button:active::before {
        content: 'Clicked';
      }
    </style>
  </head>
  <body>
    <button></button>
  </body>
</html>

Demos:

⚠️ The following GIFs contain flashing lights. People with photosensitive epilepsy beware.

The circle in the middle of the cursors indicates that VK_LBUTTON is being pressed.

@simonob
Copy link

simonob commented Apr 20, 2016

Same issue here on nwjs-v0.14.1-win-x64. Glad I found this issue, have been tweaking various bits of CSS thinking it was my fault!!

@rogerwang rogerwang added this to the 0.14.x milestone Apr 21, 2016
@rogerwang rogerwang self-assigned this Apr 21, 2016
@rogerwang
Copy link
Member

@rdtsc The report and cases are very helpful to pinpoint the root cause! Thanks again.

@rogerwang
Copy link
Member

This is fixed in git and will be available in the next nightly build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants