In my work getting CMake working on Windows, I discovered a subtle difference
in how forwarding headers are made. In the existing build system, a forwarding
header contains the entire contents of the original header. In the current
CMake build, the WEBKIT_CREATE_FORWARDING_HEADERS macro
Hi,
I'm on a slightly older pull from WebKit trunk (179714) and I'm seeing this
issue where border radius is lost if a css filter is also applied. My sample
page looks like this:
!DOCTYPE html
html
titleBasic CSS Filters/title
headBasic CSS Filters/head
style
#pic {
border-radius: 10px;
This works for me using the latest ToT build. I would recommend updating your
source tree.
--Myles
On Jul 28, 2015, at 4:52 PM, Vienneau, Christopher cvienn...@ea.com wrote:
Hi,
I’m on a slightly older pull from WebKit trunk (179714) and I’m seeing this
issue where border radius is
I think this might cause issues, because it requires the forwarding
headers be regenerated when any of the target headers change. Why does
Windows need this change? Are the headers being copied for some
packaging purpose? If so, perhaps that can be a separate step specific
to Windows.
--Martin
Hello,
I am trying to protect the MiniBrowser from executing faulty JavaScript code
taking too much time / CPU. All browsers normally raise a pop-up allowing the
user to stop the script and run away.
But MiniBrowser does not seem to have such feature. It is just stuck forever ;-(
After a
Mark, do you know how to restart JavaScript after it has reached a watchdog
time limit?
Geoff
On Jul 28, 2015, at 9:09 AM, Pascal Jacquemart p.jacquem...@samsung.com
wrote:
Hello,
I am trying to protect the MiniBrowser from executing faulty JavaScript code
taking too much time / CPU.
6 matches
Mail list logo
