| import io, re, requests, sys, time, zipfile | |
| def get_device(token): | |
| r = get("/api/v1/user/get", token) | |
| device = r.json()["user"]["devices"] | |
| print("Device: " + device, file = sys.stderr) | |
| return device | |
| def list_presences(token, device): | |
| r = get("/v4/presence/{0}/latest".format(device), token) |
| # sudo nano /lib/systemd/system/nm-resume.service | |
| # sudo systemctl enable nm-resume.service | |
| [Unit] | |
| Description=Restart NetworkManager at resume | |
| After=suspend.target | |
| After=hibernate.target | |
| After=hybrid-sleep.target | |
| [Service] | |
| ExecStart=/bin/systemctl --no-block restart NetworkManager.service |
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent