Cypress font-size difference in last decimals - font-size

I am running Cypress tests in Chrome, in Win10 and only in my environment, the font sizes are different in cypress in the last digits, like in the attached picture 1 than in Chrome.
My display settings:
100% scale
1920x1080 (Recommended) resolution
and landscape orientation
I tried to run when I used only my laptop's screen and also when I extended the desktop, but in every scenario, the same issue happened.
The following snippet results it:
element().should('have.css', 'font-size', '32px');
Do you have any idea what can produce it and how can I handle it?
Thanks

Use Electron instead of Chrome. That solved it for me.

Related

Delphi 11 - scaling and font size problems

I have a VCL application that works fine with D10.4. Created with D11, all elements of the form are displayed greatly enlarged at runtime.
Depending on the project settings (Project/Options/Manifest) you can make the program run on the development computer with a 4K monitor in the specified font (everything set to 8 points).
If you start the same program on an HD monitor, all elements except the main menu (!) are displayed in a larger font.
Windows settings on the 4K: 200% scaling, on the HD: 100%
The Delphi has all patches up to 2/22.
The exe, created with 10.4, runs perfectly on both test computers.
Is there a solution for this or do I actually have to build an own environment for VCL apps?
Is there maybe a hidden option to disable all this scaling stuff?
Thanks for every hint!
Many greetings

change screen resolution of server which runs robot framework tests from jenkins

I am currently running our robot framework UI tests via jenkins overnight.
Quite a few fail because the screen resolution it runs up in is 1024 x 768 but the tests tend to be written by people working in 1920 x 1024.
I was trying to find a way to get the server to run them on a larger screen resolution. It's a VM and I have tried setting the VM console to 1680x1050 which works for when connected on but the tests still run up in the lower resolution.
Any help appreciated!
you use "Set Window Size" keyword to set the width and height of browser from the test.

WebGL texture red and flickering on Apple devices

I'm currently in the progress of writing a simple WebGL application, where multiple textures are blended on top of each other.
The application works fine in Chrome, Firefox and IE on Windows, and also works on Android phones.
On Apple devices, however, the textures are red and flickering in any browser. I tested this on Safari on iPhone or Chrome and Firefox on a MacBook.
For example, the desired result is a wooden texture:
However, on Apple devices, this is shown:
There are no errors and no warnings from WebGL. What could be the issue or a hint to the issue here?
In this case, the solution was to initialize all variables used inside the fragment shader, which was not done correctly.

Colour of photos in different browsers?

I've just put some photos up online and I noticed that they photos appear to be a different colour in Firefox and Safari to IE and Chrome... Any ideas on what the issue could be? Due the browsers interpreter colours spaces differently or something?
Cheers
Anthony
They interpret color spaces differently because some browsers ignore ICC color profiles that are part of the images themselves. Safari and Firefox 3+ don't however, though Firefox needs to be configured to enable it.
Here's a related link: http://www.gballard.net/psd/go_live_page_profile/embeddedJPEGprofiles.html
I've noticed that png format especially differs cross browser wise. When I noticed this, I converted to jpg and it resolved it.

Adobe air window with no chrome badly calculates dimensions when maximized

When i maximize an air window that has no chrome (no system chrome, no flex chrome but i think it's the same even if only flex chrome is used) a few pixels on all sides go offscreen.
Anyone has a solution for this or knows why it happens?
It's actually easiest to set the air window to the size of the monitor, then set your custom UI to the size of the monitor minus a few pixels. That's the only workaround that I've come up with.
The only downside to this approach may be a small rendering performance loss, since the AIR window has to take alpha transparent pictures of everything behind the window, but this likely so minimal that it won't make a difference (I invite someone to benchmark this).

Resources