Hi,
Here is the latest draft of the standard:
http://dev.w3.org/csswg/css3-ui/
It looks the spec is alive, even if the discussion is not so active.
http://wiki.csswg.org/spec/css3-ui
What we should do to add new feature is described here:
http://www.webkit.org/coding/adding-features.html
Actually
+1 for runtime configuration.
Keeping code runnable is nice, and hard if it's disabled on many
developers' working copies.
We don't need to use traditional flag-holder like Settings class
and can use simple global-ish variables instead,
because We don't need to configure it per-Page basis.
I pers
>
> Even though this is out of this topic, from the point of a
> web-application developer, it would be great for WebKit to have a
> JavaScript API that encapsulates your spellchecker code so JavaScript
> can use it.
>
> Regards,
>
> Hironori Bono
> E-mail: hb...@chromi
Hi,
On Sat, Mar 5, 2011 at 11:24 AM, Dimitri Glazkov wrote:
> On Fri, Mar 4, 2011 at 12:16 PM, Ian Hickson wrote:
>> On Fri, 4 Mar 2011, Dimitri Glazkov wrote:
>>>
>>> Today, we happily use -webkit-appearance to apply platform-specific
>>> appearance to the controls. The trouble is, the value of
Hi Chromium WebKit folks,
I'm looking for a help to retrieve the latest expectation files for
Chromium Mac LayoutTest.
At the weekend there was a change that triggers massive amount of
pixel test failures that requires rebaselining.
(https://bugs.webkit.org/b/54736)
But the buildbot doesn't have t
Fabrizio, Ryan, thank you for your interest!
Although I'm suspending the work at this time, your interest gives me
a good reason to restart ;-)
I'll CC you in bug(s) and post some status there within weeks.
Regards.
morrita
On Thu, Jan 27, 2011 at 4:23 AM, Ryan Leavengood wrote:
> On Wed, J
> I think moving Platform out from WebCore is great long term goal, but right
> now, there is simply too many layering violations for it to be feasible. For
> those curious, the intent is for nothing in Platform to be dependent on
> anything else in WebCore (eg. dom, html, rendering, loader), so so
Hi, thank you for leading the reorg.
> Sources/
> automake/
> cmake/
> JavaScriptCore/
> JavaScriptGlue/
> Platform/ (was WebCore/platform)
I'd like to keep platform directory under WebCore if there is no strong reason.
Classes under WebCore/platform have WebCore namespace,
and the boundary
On Fri, Nov 19, 2010 at 4:02 AM, Maciej Stachowiak wrote:
>
> On Nov 17, 2010, at 11:44 PM, Hajime Morita wrote:
>
>> On Thu, Nov 18, 2010 at 3:51 PM, Darin Adler wrote
>>> On Nov 17, 2010, at 10:49 PM, Hajime Morita wrote:
>>>
>>>> In other word, w
On Thu, Nov 18, 2010 at 3:51 PM, Darin Adler wrote
> On Nov 17, 2010, at 10:49 PM, Hajime Morita wrote:
>
>> In other word, we should make sure that TextChecker interface can have
>> subclasses both inside and outside WebCore.
>
> Yes, in this model the abstract base c
On Thu, Nov 18, 2010 at 3:33 PM, Darin Adler wrote:
> Safari on Windows provides a spelling checker outside of WebKit. If we change
> the way spelling checking is organized inside WebKit, we need to preserve
> that feature in the WebKit used by Safari on Windows.
Thank you for pointing this out.
Hi everyone, thank you for your feedback!
Now I know there are some positive interest to Hunspell integration.
So I'll start investigation and come back once I have some progress.
@bflgham
> What would be the advantage in placing the spell checker in WebCore,
> as opposed to the relatively agnost
Hi WebKit folks,
I'm thinking about porting Hunspell-based spellchecking code
from Chromium to WebKit/WebCore.
Although it's unclear whether the porting is feasible, I'd like to
hear how much interest is there from other ports before starting
actual work.
Because the main goal is to make spellch
"pseudo-API" for mocks. This can't be
> too bad for productivity either - the social contract seems to be that you
> implement DumpRenderTree for one or two platforms at most, and file bugs for
> others.
>
> - WBR, Alexey Proskuryakov
>
>
> 27.10.2010, в
Hi Alexey, thank you for revising this topic!
I understand your concern about having a testing infrastructure inside
the production code.
On the other hand, having separate but similar mocks for each port
hurts our productivity.
And we cannot automate testing without mocks anyway.
So how about to
Hi, I'm sorry that I did it yesterday.
Usually I use webkit-patch. But that patch had 2 bug URLs and
webkit-patch didn't work for it.
So I rewrote ChangeLogs - with the wrong way.
If "webkit-patch land" support --bug-id, it might be helpful for my case.
Thanks.
--
morita
On Tue, Aug 10, 2010 at 2
Hi folks,
I posted a patch: https://bugs.webkit.org/show_bug.cgi?id=42612
Any feedbacks are appreciated.
--
morita
On Wed, Jul 21, 2010 at 2:33 PM, Hajime Morita wrote:
> Hi Maciej, thanks much for sharing your thought.
> Overall, it totally makes sense.
> And we need an actio
tionality, factor it into
> more objects, and find ways to test things that don't require quite so much
> custom functionality.
>
> I'll add on my own behalf that "layoutTestInspector" doesn't seem like a
> great name and doesn't express the relationsh
l come shortly.
--
morita
> Ojan
>
> On Wed, Jul 14, 2010 at 10:16 PM, Hajime Morita wrote:
>
>> Hi WebKit folks,
>>
>> I'm planning to add "window.layoutTestInspector" or something like that to
>> DRT.
>> And I'd like to hear your opin
Hi WebKit folks,
I'm planning to add "window.layoutTestInspector" or something like that to DRT.
And I'd like to hear your opinions.
Background:
Adding new method to LayoutTestController is hard. It
- requires to add new WebKit API to each ports, when the method is to
access WebCore.
- requires
Hi,
It looks supporting multi-threaded model.
See WebProcessLauncher.mm for detail.
--
morita
On Fri, Apr 9, 2010 at 9:11 PM, zaheer ahmad wrote:
> hi ,
> why only multi-process and not multi-thread like android. It is useful for
> mobile environments.
> thanks,
> Zaheer
>
> On Fri, Apr 9, 2010
or code for that, which would be very helpful.
I'll follow the progress of our implementation.
--
morita
On Mon, Apr 5, 2010 at 11:31 AM, Maciej Stachowiak wrote:
>
> On Apr 4, 2010, at 7:23 PM, Hajime Morita wrote:
>
>> Hi folks,
>>
>> I'm planning to wo
Hi folks,
I'm planning to work on HTML5 element,
which is filed on https://bugs.webkit.org/show_bug.cgi?id=37074 .
Although there seems no effort for that element at this time,
The element looks similar to .
So I'll try to go the way as has been going and
share some part of codebase hopefully.
23 matches
Mail list logo
