Bug 89235 [1] notes lack of support for the CSS3 Text module's line-break
property. I have prepared a patch to add support for the values expressed
by this property to the existing -webkit-line-break property, as a
preliminary step before the CSSWG agrees to unprefixed usage of CSS3 Text
properties
On Sep 4, 2012, at 10:19 AM, noam.rosent...@nokia.com wrote:
> A
> On Sep 4, 2012, at 8:34 AM, ext Konstantin Tokarev wrote:
>
>>>
>>> To get it compiling, I had to patch ANGLE source code and Simon Hausmann
>>> told
>>> me he is not comfortable in reviewing these patches. So here I am asking
On Wed, Sep 5, 2012 at 12:44 PM, Adam Barth wrote:
> On Wed, Sep 5, 2012 at 3:23 AM, Patrick Gansterer wrote:
>> On Tue, 04 Sep 2012 22:26:52 -0700, Adam Barth wrote:
>>>
>>> On Tue, Sep 4, 2012 at 10:06 PM, Christophe Dumez
>>> wrote:
On Sep 5, 2012, at 2:22 AM, Adam Barth wrote:
>>>
On Wed, Sep 5, 2012 at 3:23 AM, Patrick Gansterer wrote:
> On Tue, 04 Sep 2012 22:26:52 -0700, Adam Barth wrote:
>>
>> On Tue, Sep 4, 2012 at 10:06 PM, Christophe Dumez
>> wrote:
>>>
>>> On Sep 5, 2012, at 2:22 AM, Adam Barth wrote:
Removing operator+= will likely require changes to a
This is an unlikely situation to occur in real web pages, so there is neither
much risk nor much benefit to this change. One way this could break a page is
if it calculates a URL and erroneously ends up with a null. In this case,
raising an exception would further break page logic - instead of g
On Tue, 04 Sep 2012 22:26:52 -0700, Adam Barth wrote:
On Tue, Sep 4, 2012 at 10:06 PM, Christophe Dumez
wrote:
On Sep 5, 2012, at 2:22 AM, Adam Barth wrote:
Removing operator+= will likely require changes to a number of
port-specific files. I'll do my best to remove these, but I might
need s
6 matches
Mail list logo
