On Wed, Jun 27, 2018 at 8:05 PM Adam Barth wrote:
>
> Hi Yusuke,
>
> For some reason, your original email missed my inbox.
>
> On Wed, Jun 27, 2018 at 7:53 PM Michael Catanzaro
> wrote:
> > On Tue, Jun 26, 2018 at 6:49 PM, Yusuke SUZUKI
> > wrote:
> >
Hi Yusuke,
For some reason, your original email missed my inbox.
On Wed, Jun 27, 2018 at 7:53 PM Michael Catanzaro wrote:
> On Tue, Jun 26, 2018 at 6:49 PM, Yusuke SUZUKI
> wrote:
> > My suggestion is introducing Fushcia port, adding both
> > PLATFORM(FUSHCIA) and OS(FUSHCIA) ifdefs.
> > Use
thoughts inline:
>
> > On Jun 26, 2018, at 2:00 PM, Adam Barth wrote:
> >
> > As part of developing Fuchsia [1] (a new open-source operating
> > system), we ported JavaScriptCore to run on Fuchsia [2]. At the time,
> > our intent was to use this code within the F
As part of developing Fuchsia [1] (a new open-source operating
system), we ported JavaScriptCore to run on Fuchsia [2]. At the time,
our intent was to use this code within the Fuchsia source tree but not
to make it available for developers writing applications for Fuchsia.
However, recently,
For what it's worth, we didn't receive any negative feedback from
users or developers when we dropped support for this feature in
Chrome.
Adam
On Tue, Apr 21, 2015 at 3:39 PM, Chris Dumez cdu...@apple.com wrote:
Hi,
I would like to suggest we remove support for 'multipart/x-mixed-replace’
On Apr 1, 2015 9:29 PM, Brent Fulgham bfulg...@apple.com wrote:
The Windows EWS bots process patches fairly quickly. Once I corrected the
problem today, it managed to process about 97 patches in about an hour.
I do think one bottleneck is due to individual EWS bots “locking”
patches. The first
Hi Ryosuke,
On Sat, Feb 15, 2014 at 4:07 PM, Ryosuke Niwa rn...@webkit.org wrote:
Now that we've removed all of the existing shadow DOM implementations from
trunk in http://trac.webkit.org/changeset/164131, I'm intending to work
on new web components implementations in a branch based on the
On Tue, Feb 18, 2014 at 1:41 PM, Ryosuke Niwa rn...@webkit.org wrote:
On Tue, Feb 18, 2014 at 7:44 AM, Adam Barth aba...@webkit.org wrote:
On Sat, Feb 15, 2014 at 4:07 PM, Ryosuke Niwa rn...@webkit.org wrote:
Now that we've removed all of the existing shadow DOM implementations
from trunk
On Tue, Feb 18, 2014 at 2:41 PM, Adam Barth aba...@webkit.org wrote:
On Tue, Feb 18, 2014 at 1:54 PM, Maciej Stachowiak m...@apple.com wrote:
Do you have any more specific pointers that Ryosuke et al could look at
for the O(N^2) algorithm? Like a commit range or a function to look
On Feb 18, 2014 3:59 PM, Ryosuke Niwa rn...@webkit.org wrote:
On Tue, Feb 18, 2014 at 3:09 PM, Adam Barth aba...@webkit.org wrote:
On Tue, Feb 18, 2014 at 2:41 PM, Adam Barth aba...@webkit.org wrote:
On Tue, Feb 18, 2014 at 1:54 PM, Maciej Stachowiak m...@apple.com
wrote:
Do you have any
Neat! Over in Blink-land, we're also quite interested in infinite
scrolling. Do you have a doc that describes the approach you're
investigating?
We've been experimenting with how you might be able to achieve infinite
scrolling using existing web platform API. You can see the engine we're
On Jan 28, 2014 4:19 PM, Edward O'Connor eocon...@apple.com wrote:
Hi,
Adam wrote:
Over in Blink-land, we're also quite interested in infinite scrolling.
Great! It's an increasingly common pattern that could use some help from
the engine.
We've been experimenting with how you might be
On Fri, Oct 4, 2013 at 12:08 PM, Dean Jackson d...@apple.com wrote:
On 3 Oct 2013, at 4:46 am, Christian Biesinger cbiesin...@chromium.org
wrote:
On Tue, Oct 1, 2013 at 8:26 PM, Ryosuke Niwa rn...@webkit.org wrote:
On Tue, Oct 1, 2013 at 4:53 PM, James Craig jcr...@apple.com wrote:
On Fri, Oct 4, 2013 at 1:37 PM, Dean Jackson d...@apple.com wrote:
On 5 Oct 2013, at 6:22 am, Adam Barth aba...@webkit.org wrote:
On Fri, Oct 4, 2013 at 12:08 PM, Dean Jackson d...@apple.com wrote:
On 3 Oct 2013, at 4:46 am, Christian Biesinger cbiesin...@chromium.org
wrote:
On Tue, Oct 1
On Sun, Aug 25, 2013 at 11:41 AM, Geoffrey Garen gga...@apple.com wrote:
The blink people are running into a bunch of issues by implementing them on
the C++ side as opposed to inside the VM.
I don’t think we can reason by analogy here.
Is there a specific problem you’re concerned about?
Very impressive.
If (like me) you're curious about what changes to WebKit are required
to make this work, I found the diff at the following URL:
https://github.com/nacl-webkit/webkit/compare/upstream_base...master
Adam
On Sun, Jun 30, 2013 at 11:41 PM, halton huo halton@gmail.com wrote:
On Fri, May 31, 2013 at 3:18 PM, Darin Adler da...@apple.com wrote:
On May 31, 2013, at 1:57 PM, Brendan Long s...@brendanlong.com wrote:
I hope this isn't a stupid question, but I can't find any references to what
the difference between AtomicString and String is.
WTF::AtomicString is a
On Thu, Apr 11, 2013 at 12:07 AM, Ryosuke Niwa rn...@webkit.org wrote:
On Wed, Apr 10, 2013 at 11:48 PM, Osztrogonác Csaba o...@inf.u-szeged.hu
wrote:
Just out of curiosity, isn't simpler deliver the ownership of
these apps from Google to Apple instead of starting new apps?
We can't because
- Commit queue (now uses Mac WebKit port instead of Chromium Linux
port)
- Feeder queue
- Style queue
- webkitbot (renamed from sheriffbot)
- Flakiness dashboard: webkit-test-resuls.appspot.com
^^^ Is that a typo? (resuls - results)
I want to personally thank Adam Barth
Chromium is not interested in supporting APNG. I'm not opposed to landing
this patch if other ports are interested in supporting APNG.
Adam
On Mar 21, 2013 4:28 AM, Allan Sandfeld Jensen k...@carewolf.com wrote:
On Thursday 21 March 2013, Max Stepin wrote:
What do you think?
I posted
On Sun, Mar 17, 2013 at 8:56 PM, Geoffrey Garen gga...@apple.com wrote:
Unfortunately, you can't implement CSP that way.
:(
OK, let's consider this a proposal for how the disable javascript setting
should behave, and leave CSP out of it.
Consider the case of
two same-origin iframes A
Unfortunately, you can't implement CSP that way. Consider the case of
two same-origin iframes A and B. Suppose A has a restrictive CSP
policy (say that bans everything) and B doesn't. If B uses the DOM to
insert a script element into A, then CSP should block that script
element from executing.
On Tue, Mar 12, 2013 at 1:36 AM, Osztrogonác Csaba o...@inf.u-szeged.hu wrote:
But my question is still open about how can we avoid similar
problems in the future. Why can't we let the EWS bots to
build and test security patches before commit.
This topic was discussed on the webkit-security
On Tue, Mar 12, 2013 at 2:26 AM, Maciej Stachowiak m...@apple.com wrote:
On Mar 12, 2013, at 1:48 AM, Adam Barth aba...@webkit.org wrote:
On Tue, Mar 12, 2013 at 1:36 AM, Osztrogonác Csaba o...@inf.u-szeged.hu
wrote:
But my question is still open about how can we avoid similar
problems
Stachowiak m...@apple.com wrote:
On Mar 9, 2013, at 3:05 PM, Adam Barth aba...@webkit.org wrote:
In retrospect, I think what I was reacting to was msaboff statement
that an unnamed group of people had decided that the HTML tokenizer
was too unwieldy to have a dedicated 8-bit path. In particular
On Mon, Mar 11, 2013 at 9:56 AM, Darin Adler da...@apple.com wrote:
On Mar 11, 2013, at 9:54 AM, Adam Barth aba...@webkit.org wrote:
If you're about to reply complaining about the above, please save your
complaints for another time.
Huh?
The last time we tried to talk about changing
.
On Mar 7, 2013, at 2:16 PM, Adam Barth aba...@webkit.org wrote:
Yes, I understand how the HTML tokenizer works. :)
I didn't understand these details, and I really appreciate Michael
describing them. I'm also glad others on the mailing list had an
opportunity to get something out of this.
I
On Sat, Mar 9, 2013 at 5:02 PM, Maciej Stachowiak m...@apple.com wrote:
On Mar 8, 2013, at 3:09 PM, Adam Barth aba...@webkit.org wrote:
I've posted a patch to limit the -apple- and -khtml- CSS vendor
prefixes to ENABLE(DASHBOARD_SUPPORT):
https://bugs.webkit.org/show_bug.cgi?id=111890
My
On Sat, Mar 9, 2013 at 8:55 PM, Maciej Stachowiak m...@apple.com wrote:
On Mar 9, 2013, at 8:00 PM, Adam Barth aba...@webkit.org wrote:
On Sat, Mar 9, 2013 at 5:02 PM, Maciej Stachowiak m...@apple.com wrote:
My recommendation would be:
* Do one of the following two options:
- Plan
don't want
developers doing that.
On Feb 28, 2013, at 6:02 PM, Adam Barth aba...@webkit.org wrote:
I noticed this comment on the Hacker News thread about Paul Irish's
recent blog post:
---8---
CSS parsing is the same, though. Slurping up your CSS and turning it
into CSSOM’s pretty standard
The HTMLTokenizer still works in UChars. There's likely some
performance to be gained by moving it to an 8-bit character type.
There's some trickiness involved because HTML entities can expand to
characters outside of Latin-1. Also, it's unclear if we want two
tokenizers (one that's 8 bits wide
zero extension
happens for an 8 bit sub string.
My research showed that at the time showed that there were very few UTF-16
only resources (5% IIRC), although I expect the number to grow.
- Michael
On Mar 7, 2013, at 11:11 AM, Adam Barth aba...@webkit.org wrote:
The HTMLTokenizer still
Have you proposed this feature to the relevant standards working group?
Adam
On Mon, Mar 4, 2013 at 4:37 PM, Jer Noble jer.no...@apple.com wrote:
In an effort to improve the user-experience of watching videos in full screen
mode, I have created a patch which adds a new CSS style attribute:
I noticed this comment on the Hacker News thread about Paul Irish's
recent blog post:
---8---
CSS parsing is the same, though. Slurping up your CSS and turning it
into CSSOM’s pretty standard. Yeah, though Chrome accepts just the
-webkit- prefix whereas Apple and other ports accept legacy
On Sat, Feb 16, 2013 at 11:26 PM, Dirk Schulze dschu...@adobe.com wrote:
On Feb 16, 2013, at 10:50 PM, Maciej Stachowiak m...@apple.com wrote:
On Feb 16, 2013, at 10:16 PM, Dirk Schulze dschu...@adobe.com wrote:
On Feb 16, 2013, at 6:54 PM, Adam Barth aba...@webkit.org wrote:
It's much easier
On Sun, Feb 17, 2013 at 7:26 AM, Dirk Schulze dschu...@adobe.com wrote:
On Feb 17, 2013, at 1:28 AM, Maciej Stachowiak m...@apple.com wrote:
On Feb 17, 2013, at 1:09 AM, Filip Pizlo fpi...@apple.com wrote:
On Feb 17, 2013, at 1:04 AM, Dirk Schulze dschu...@adobe.com wrote:
The discussion on
It's much easier to discuss a concrete example. Which interface are
you interested in deprecating?
Adam
On Sat, Feb 16, 2013 at 5:28 PM, Dirk Schulze dschu...@adobe.com wrote:
Hi,
There are several steps on deprecating features[1]. My question is about
deprecating a whole interface and
On Sun, Feb 10, 2013 at 10:39 AM, Ojan Vafai o...@chromium.org wrote:
On Sat, Feb 9, 2013 at 7:41 PM, Maciej Stachowiak m...@apple.com wrote:
Hi Peter,
On Feb 9, 2013, at 3:48 PM, Peter Kasting pkast...@google.com wrote:
On Sat, Feb 9, 2013 at 11:52 AM, Maciej Stachowiak m...@apple.com
On Fri, Feb 8, 2013 at 8:19 PM, Maciej Stachowiak m...@apple.com wrote:
On Feb 8, 2013, at 2:33 PM, Darin Fisher da...@chromium.org wrote:
I would recommend minimizing the re-architecture of WebCore as you are in
the early stages of upstreaming. It seems like you already have a working
Context: https://bugs.webkit.org/show_bug.cgi?id=109071
Adam Barth said:
It's not clear to me that running WebCore on multiple interlocked threads is
a good idea. That
seems like a pretty major change to WebCore's architecture. Is that
something that's up for
discussion?
Darin Adler
On Fri, Feb 8, 2013 at 2:45 PM, David Kilzer ddkil...@webkit.org wrote:
On Feb 8, 2013, at 1:41 PM, Adam Barth aba...@webkit.org wrote:
Context: https://bugs.webkit.org/show_bug.cgi?id=109071
Adam Barth said:
It's not clear to me that running WebCore on multiple interlocked threads
is a good
On Fri, Feb 8, 2013 at 4:07 PM, David Kilzer ddkil...@webkit.org wrote:
On Feb 8, 2013, at 2:52 PM, Adam Barth aba...@webkit.org wrote:
On Fri, Feb 8, 2013 at 2:45 PM, David Kilzer ddkil...@webkit.org wrote:
The iOS port does not require re-architecting WebCore.
Bug 109071 was about coming up
On Fri, Feb 8, 2013 at 4:29 PM, Pratik Solanki psola...@apple.com wrote:
On Feb 8, 2013, at 4:14 PM, Adam Barth aba...@webkit.org wrote:
On Fri, Feb 8, 2013 at 4:07 PM, David Kilzer ddkil...@webkit.org wrote:
On Feb 8, 2013, at 2:52 PM, Adam Barth aba...@webkit.org wrote:
On Fri, Feb 8, 2013
On Fri, Feb 8, 2013 at 4:56 PM, Maciej Stachowiak m...@apple.com wrote:
On Feb 8, 2013, at 4:14 PM, Adam Barth aba...@webkit.org wrote:
On Fri, Feb 8, 2013 at 4:07 PM, David Kilzer ddkil...@webkit.org wrote:
On Feb 8, 2013, at 2:52 PM, Adam Barth aba...@webkit.org wrote:
On Fri, Feb 8, 2013
We should check whether IE still have that behavior (i.e., in the
latest version of IE). I remember them running into some
compatibility problems with that aspect of nosniff, and I'm not sure
if they resolved those issue via evangelism or by adopting our
behavior.
Adam
On Wed, Feb 6, 2013 at
On Wed, Feb 6, 2013 at 4:59 PM, Alec Flett alecfl...@chromium.org wrote:
On Wed, Feb 6, 2013 at 4:48 PM, Maciej Stachowiak m...@apple.com wrote:
I think we should continue to use uint8_t instead of char as the primary
way to represent a raw byte in WebKit. First, it's good to distinguish raw
Do you know how they got rid of flakiness in their tests? We've spent
a bunch of effort fixing flaky tests (and in marking the remaining
flaky tests as flaky), but there's still a long tail of flakiness. I
wonder if that sort of thing might be different for OpenStack if they
have a different
Given the consistency of other user agents, this looks like the right thing
to do for the web. We should try it in Canary to see if it's compatible
with the web.
Adam
On Feb 4, 2013 5:05 AM, Mike West mk...@chromium.org wrote:
Way back in the depths of 2010, Mihai suggested that we begin to
On Sun, Feb 3, 2013 at 11:34 AM, noam.rosent...@nokia.com wrote:
On 2/3/13 7:46 PM, ext Maciej Stachowiak m...@apple.com wrote:
If you're asking about phasing it out entirely, we don't have any
immediate plans to deprecate or remove the WebKit1 mac API. There are
quite a few Apple and
On Sun, Feb 3, 2013 at 11:46 AM, Adam Barth aba...@webkit.org wrote:
On Sun, Feb 3, 2013 at 11:34 AM, noam.rosent...@nokia.com wrote:
On 2/3/13 7:46 PM, ext Maciej Stachowiak m...@apple.com wrote:
If you're asking about phasing it out entirely, we don't have any
immediate plans to deprecate
Ninja has extremely fast incremental builds and can be generated by
GYP. Here are some stats from a year ago:
https://plus.google.com/101038813433650812235/posts/irc26fhRtPC
Ninja has gotten even faster since then. If you're interested in
trying it out, you can play around with incremental
On Thu, Jan 31, 2013 at 12:25 AM, Mark Rowe mr...@apple.com wrote:
On 2013-01-30, at 17:14, Dirk Pranke dpra...@chromium.org wrote:
On Wed, Jan 30, 2013 at 4:15 PM, Maciej Stachowiak m...@apple.com wrote:
On Jan 30, 2013, at 3:24 PM, Dirk Pranke dpra...@chromium.org wrote:
On Wed, Jan 30, 2013
On Tue, Jan 29, 2013 at 11:58 PM, Maciej Stachowiak m...@apple.com wrote:
I agree that the regression should be fixed. But before we discuss that...
I am puzzled by the apparent stance of Alexey must immediately fix this
himself or we must revert immediately. That's not the standard we have
I understand that the new rules of the road for WebKit2 are that
contributors are allowed to break non-Apple ports. However, those new
norms do not extend to WebCore.
In http://trac.webkit.org/changeset/138962, Alexey broke form
resubmission confirmation in the Chromium port. In
Our general approach to deprecating features is outlined on this wiki page:
http://trac.webkit.org/wiki/DeprecatingFeatures
It sounds like you're advocating the cold turkey approach here with
a clear path forward for developers.
Adam
On Tue, Jan 29, 2013 at 5:46 PM, Dirk Schulze
:
On Jul 25, 2012, at 3:50 PM, Adam Barth wrote:
On Wed, Jul 25, 2012 at 3:44 PM, Dirk Schulze dschu...@adobe.com wrote:
On Jul 25, 2012, at 2:33 PM, Adam Barth wrote:
Eric Seidel points out that SVG uses multiple inheritance in its DOM
interfaces. However, the situation there is a bit different
On Fri, Jan 25, 2013 at 11:28 AM, Glenn Adams gl...@skynav.com wrote:
On Fri, Jan 25, 2013 at 10:14 AM, Adam Barth aba...@webkit.org wrote:
There's no experiment that you can run using web content to detect
whether we implement WebIDL. All you can detect is whether we
implement particular
On Fri, Jan 25, 2013 at 2:08 PM, Dirk Schulze dschu...@adobe.com wrote:
On Jan 25, 2013, at 9:14 AM, Adam Barth aba...@webkit.org wrote:
On Fri, Jan 25, 2013 at 8:11 AM, Dirk Schulze dschu...@adobe.com wrote:
This is a followup to the multiple inheritance discussion.
Adam, I checked the IDL
On Fri, Jan 25, 2013 at 8:59 PM, Elliott Sprehn espr...@chromium.org wrote:
On Fri, Jan 25, 2013 at 11:32 PM, Dirk Schulze dschu...@adobe.com wrote:
...
The problem is that SVGFitToViewBox and SVGZoomAndPan of the example above
are implemented by a lot of other interfaces as well. Supplemental
Thanks for the note. We seem to have a temp file leak in
run-webkit-tests. I'm rebuilding the machines now.
Adam
On Thu, Jan 24, 2013 at 10:03 AM, Dumez, Christophe
christophe.du...@intel.com wrote:
Hi,
It appears the commit queue stopped working due to lack of disk space:
Note that WebKit re-uses the same Document after a call to
document.open(). I suspect we're unlikely to change that behavior
anytime soon.
Adam
On Thu, Jan 24, 2013 at 12:59 PM, Anne van Kesteren ann...@annevk.nl wrote:
Hi,
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20567 could use
On Thu, Jan 24, 2013 at 7:13 PM, Geoffrey Garen gga...@apple.com wrote:
Note that WebKit re-uses the same Document after a call to
document.open(). I suspect we're unlikely to change that behavior
anytime soon.
Do we know of any websites that depend on this behavior?
I haven't tested this
of
different browsers.
I know there's some amount of confusion about the current status of
the web notification APIs. I'm working with Chrome's developer
relation folks to update our various pieces of documentation and
tutorials.
Adam
On Wed, Jan 23, 2013 at 1:47 AM, Adam Barth aba
notification APIs, though. I'll get the ball rolling on gmail, at least.
Thanks! Let me know if you run into any trouble.
Adam
On Wed, Jan 23, 2013 at 9:58 AM, Adam Barth aba...@webkit.org wrote:
On Wed, Jan 23, 2013 at 12:45 AM, Andrew Wilson atwil...@google.com
wrote:
Hmmm. Does
as
well.
Adam
On Jan 23, 2013, at 1:11 AM, Adam Barth aba...@webkit.org wrote:
On Wed, Jan 23, 2013 at 1:08 AM, Andrew Wilson atwil...@google.com wrote:
Apologies for the confusion - I should have finished my coffee before
reading my mail. I didn't realize this only impacts HTML notifications
As discussed in February 2012 [1], we have been deprecating the
webkitNotifications.createHTMLNotification API for almost a year.
According to FeatureObserver, the API is used in only 0.0008% of web
page views, indicating that we have been successful in depreciating
it. I've posted a patch to
you all are feeling
less schedule pressure.
Adam
On Sun, Jan 20, 2013 at 11:44 PM, Adam Barth aba...@webkit.org wrote:
On Sun, Jan 20, 2013 at 1:54 PM, Maciej Stachowiak m...@apple.com wrote:
On Jan 20, 2013, at 1:44 PM, Adam Barth aba...@webkit.org wrote:
On Sun, Jan 20, 2013 at 1:30 PM
On Wed, Jan 16, 2013 at 11:33 PM, Maciej Stachowiak m...@apple.com wrote:
On Jan 12, 2013, at 1:14 AM, Adam Barth aba...@webkit.org wrote:
On Sat, Jan 12, 2013 at 12:03 AM, Maciej Stachowiak m...@apple.com wrote:
Do you think thread in the UI process vs. completely separate process
On Sun, Jan 20, 2013 at 1:30 PM, Oliver Hunt oli...@apple.com wrote:
I take your word for it that it's not possible on Windows.
Given that Chromium has many users on Windows (and other non-Mac
platforms), you should now understand why this design does not fit
well with Chromium's design
On Sun, Jan 20, 2013 at 1:54 PM, Maciej Stachowiak m...@apple.com wrote:
On Jan 20, 2013, at 1:44 PM, Adam Barth aba...@webkit.org wrote:
On Sun, Jan 20, 2013 at 1:30 PM, Oliver Hunt oli...@apple.com wrote:
I take your word for it that it's not possible on Windows.
Given that Chromium
Have you tried uploading the patch manually by running
svn-create-patch and using the attachments UI in bugs.webkit.org?
One possibility is that your patch is too big for bugs.webkit.org to
handle. You mention that it contains a number of binary files, which
might be the cause of the problem.
Maybe we shouldn't bother feeding the bots patches that are over a
certain age (perhaps a week)?
Adam
On Thu, Jan 17, 2013 at 11:50 AM, Eric Seidel e...@webkit.org wrote:
I believe the queue was actually cleared when they were brought
online. As Ossy notes, this is expected behavior.
Every
Maciej has asked that we keep it around until the end of February:
https://bugs.webkit.org/show_bug.cgi?id=100710
Adam
On Thu, Jan 17, 2013 at 4:10 PM, Ryosuke Niwa rn...@webkit.org wrote:
Hi,
It has been 11 months since Eric initially raised the concern. Can we go
ahead and remove the
We more or less ignore the is confirmed bit in bugs.webkit.org.
Adam
On Wed, Jan 16, 2013 at 6:35 AM, 徐征 xz91...@yahoo.co.jp wrote:
Hello everyone
This is Zheng and nice to meet you.
I want to confirm some
issue(https://bugs.webkit.org/show_bug.cgi?id=78957) and try to create
patch for
/12 16:55 , Adam Barth wrote:
My sense is that the WebKit community would prefer that the
hashes in
GitHub match the hashes in git.webkit.org
http://git.webkit.org so that folks can more
easily move branches between the two. For my part, I've
On Mon, Jan 14, 2013 at 12:51 AM, Steve Williams
stephen.j.h.willi...@googlemail.com wrote:
1. It's been on your bug database for ages hence filing another entry won't
move anything forwards.
2. svg 1.1 spec seems a little over the top in places so not personally
interested in full support -
On Mon, Jan 14, 2013 at 8:39 AM, Dominik Röttsches
dominik.rottsc...@intel.com wrote:
when we land https://bugs.webkit.org/show_bug.cgi?id=106774
we'll have to do a large rebaseline of EFL results. (subpixel and FreeType
related change)
Now, for landing, what we had in mind is, (optionally)
On Sat, Jan 12, 2013 at 12:03 AM, Maciej Stachowiak m...@apple.com wrote:
On Jan 11, 2013, at 2:53 PM, Adam Barth aba...@webkit.org wrote:
On Fri, Jan 11, 2013 at 2:19 AM, Maciej Stachowiak m...@apple.com wrote:
On Jan 11, 2013, at 12:21 AM, Adam Barth aba...@webkit.org wrote:
Is that really
On Thu, Jan 10, 2013 at 9:19 PM, Maciej Stachowiak m...@apple.com wrote:
On Jan 10, 2013, at 12:07 PM, Adam Barth aba...@webkit.org wrote:
On Thu, Jan 10, 2013 at 12:37 AM, Maciej Stachowiak m...@apple.com wrote:
I presume from your other comments that the goal of this work is
responsiveness
That does sound like a tricky problem. Your approach sounds
reasonable to me. If you like, we can use the FeatureObserver [1] to
estimate how often these various cases occur.
Adam
[1] http://lists.webkit.org/pipermail/webkit-dev/2012-September/022239.html
On Fri, Jan 11, 2013 at 11:30 AM,
On Fri, Jan 11, 2013 at 2:19 AM, Maciej Stachowiak m...@apple.com wrote:
On Jan 11, 2013, at 12:21 AM, Adam Barth aba...@webkit.org wrote:
If you're actually planning to make a significant complexity-imposing
architectural change for performance reasons, without any way to test
whether
Thanks everyone for your feedback. Detailed responses inline.
On Wed, Jan 9, 2013 at 9:41 PM, Filip Pizlo fpi...@apple.com wrote:
I think your biggest challenge will be ensuring that the latency of shoving
things to another core and then shoving them back will be smaller than the
latency of
The solution I'd recommend is to make the JavaScriptCore and/or
WebKit2 bots faster. If those bots are able to complete their
processing before the commit-queue, then they'll stop the patch from
being committed by marking the patch commit-queue-.
Adam
On Thu, Jan 10, 2013 at 9:22 PM, Ryosuke
On Wed, Jan 9, 2013 at 6:00 PM, Eric Seidel e...@webkit.org wrote:
We're planning to move parts of the HTML Parser off of the main thread:
https://bugs.webkit.org/show_bug.cgi?id=106127
This is driven by our testing showing that HTML parsing on mobile is
be slow, and long (causing
On Wed, Jan 9, 2013 at 7:35 PM, Benjamin Poulain benja...@webkit.org wrote:
On Wed, Jan 9, 2013 at 7:07 PM, Eric Seidel e...@webkit.org wrote:
On Wed, Jan 9, 2013 at 6:38 PM, Oliver Hunt oli...@apple.com wrote:
How will we ensure thread safety? Even at just the tokenizing level
don't we use
Based on our discussion in September, the Chromium port has been
shipping for a while with webkitPostMessage compiled out. We've been
monitoring our support channels and haven't found any reports of
compatibility problems. (By way of comparison, we did find some
compatibility problems with
On Wed, Dec 5, 2012 at 10:44 PM, Alexander Pavlov apav...@chromium.org wrote:
On Thu, Dec 6, 2012 at 5:36 AM, Dana Jansens dan...@chromium.org wrote:
On Wed, Dec 5, 2012 at 8:28 PM, Adam Barth aba...@webkit.org wrote:
On Wed, Dec 5, 2012 at 7:16 AM, Alexander Pavlov apav...@chromium.org
On Wed, Dec 5, 2012 at 7:16 AM, Alexander Pavlov apav...@chromium.org wrote:
I'm working on emulating the device scale factor with Web Inspector. My goal
is to let web developers see their pages on normal (device pixel ratio ==
1) monitors the way they would look on e.g. retina screens.
There's some problem with the commit-queue failing with some git
error. I'm taking it offline for the rest of the day. Hopefully I'll
figure it out tonight.
Adam
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
failures can be found here:
http://queues.webkit.org/results/15120956
(For any with git-knowledge who might know what's wrong.)
On Tue, Dec 4, 2012 at 12:36 PM, Adam Barth aba...@webkit.org wrote:
There's some problem with the commit-queue failing with some git
error. I'm taking it offline
There's been a somewhat fragmented discussion across webkit-dev and
various bugs about how we ought to approach multiprocess networking in
WebKit. In an attempt to organize my thoughts, I wrote up a short
design document that compares various approaches:
On Wed, Nov 28, 2012 at 5:53 PM, Benjamin Poulain benja...@webkit.org wrote:
On Wed, Nov 28, 2012 at 8:23 AM, Adam Barth aba...@webkit.org wrote:
I'm sympathetic to these concerns, but, unfortunately, I don't see any
other path that leads to interoperability with Internet Explorer.
Currently
On Thu, Nov 29, 2012 at 9:23 PM, Glenn Adams gl...@skynav.com wrote:
On Thu, Nov 29, 2012 at 10:00 PM, Ryosuke Niwa rn...@webkit.org wrote:
On Thu, Nov 29, 2012 at 8:55 PM, Glenn Adams gl...@skynav.com wrote:
On Wed, Nov 28, 2012 at 1:31 PM, Rafael Weinstein rafa...@chromium.org
wrote:
Hello,
On Wed, Nov 28, 2012 at 3:53 AM, Tor Arne Vestbø
tor.arne.ves...@digia.com wrote:
On 11/25/12 1:12 , Adam Barth wrote:
On Sat, Nov 24, 2012 at 1:53 PM, Gergely Kis gerg...@homejinni.com
wrote:
Yes, I saw that thread, but I got confused by this other thread:
https://lists.webkit.org/pipermail
It looks like this thread got dropped over Thanksgiving. (Responses inline.)
On Thu, Nov 22, 2012 at 1:43 PM, Benjamin Poulain benja...@webkit.org wrote:
On Wed, Nov 21, 2012 at 2:42 PM, Rick Byers rby...@chromium.org wrote:
Outside of the design details, are there any thoughts or concerns
Sounds like a reasonable idea. Would you be willing to file a bug and
write a patch?
Adam
On Mon, Nov 26, 2012 at 3:18 PM, Marshall Greenblatt
magreenbl...@gmail.com wrote:
Hi All,
Applications embedding WebKit and Chromium can use existing C++ APIs
to dynamically add custom V8 JavaScript
On Sat, Nov 24, 2012 at 1:53 PM, Gergely Kis gerg...@homejinni.com wrote:
Yes, I saw that thread, but I got confused by this other thread:
https://lists.webkit.org/pipermail/webkit-dev/2012-April/020339.html
Here most of the participants seemed to agree that moving the 2 repositories
to use
On Thu, Nov 15, 2012 at 4:28 PM, Mike Lawther mikelawt...@google.com wrote:
On 16 November 2012 09:59, Ryosuke Niwa rn...@webkit.org wrote:
While I don’t want to further agitate the issue or go off on a tangent,
and agree that we must address the security aspect before getting rid of
On Sun, Nov 11, 2012 at 6:09 PM, Hajime Morrita morr...@chromium.org wrote:
IIRC, Android (non-Chrome) uses V8. I'm not sure whether PLATFORM(CHROMIUM)
is on there.
non-Chromium Android is no longer supported on trunk.
On Sun, Nov 11, 2012 at 6:32 PM, Ryosuke Niwa rn...@webkit.org wrote:
The
DOMImplementation : public ScriptWrappable {
I'm not super excited about the name given that all DOM objects are
wrappable by script. If folks have thoughts about a better name, I'd
appreciate suggestions.
Thanks,
Adam
On Thu, Nov 1, 2012 at 10:36 AM, Adam Barth aba...@webkit.org wrote:
We currently use
1 - 100 of 1121 matches
Mail list logo
