Re: [webkit-dev] Request for Position: CSS Text Decoration Module for SVG

[Cameron McCormack via webkit-dev]

Hi Kent,

> I'd like to request an official WebKit position on expanding support of "CSS 
> Text Decoration Module" [1] for SVG .  Currently WebKit and Blink 
> support only a few features for SVG , and we'd like to add support of 
> features which are currently supported for HTML.
> 
> Firefox already supports various properties for SVG , including 
> text-emphasis-style.

We are in support of this. In general, CSS text properties should all apply to 
SVG text too, unless there is a specific reason/conflict. Please note that CSS 
properties that newly apply to SVG text should not gain presentation 
attributes, per the note below the table in 
https://svgwg.org/svg2-draft/styling.html#PresentationAttributes 
.

Cameron

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Optional parameter in IDL and undefined JS value

[Cameron McCormack]

Jian Li:
  I am referring to Blob.slice(start, end) that mimics Array.slice. Where in
  WebIDL has this behavior defined? Sorry I can't find it in the spec.
 
  For Array.slice(start, end), both Safari and Chrome treat passing undefined
  as omitted parameter, while Firefox and IE treat passing undefined as 0.

Ryosuke Niwa:
 Doesn't that mean the current behavior (i.e. treating undefined as 0) is
 correct since that's what other browsers do?

The File API spec currently says:

  Blob slice(in optional long long start,
 in optional long long end,
 in optional DOMString contentType);

and Web IDL says that if you call

  blob.slice(10, undefined);

then this is calling the function with two arguments, where the second
argument will be converted to 0 due to how the conversion of JS
undefined to an IDL long long value is defined.  This is not the same as
calling

  blob.slice(10);

Whenever some optional arguments are omitted, the prose for the
definition of the operation defines what that means; it’s not
automatically “convert from undefined”.

There is no way in Web IDL to state that when undefined is passed as an
argument explicitly that it is handled differently from the rules in
http://dev.w3.org/2006/webapi/WebIDL/#es-type-mapping (although the
authors of the File API spec could include this additional requirement
in prose, overriding Web IDL, if they wanted).

-- 
Cameron McCormack ≝ http://mcc.id.au/
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] [svg] rect with invalid stroke value

[Cameron McCormack]

Nikolas Zimmermann:
 We had 'none' for years, until compatibility bugs were raised, as
 Opera uses black as default stroke, if there is any error.

Doesn’t seem to be the case any more, at least for Opera 10.53:

http://livedom.validator.nu/?%3C!DOCTYPE%20html%3E%0D%0A%3Csvg%20width%3D'100'%20height%3D'100'%3E%3Ccircle%20cx%3D'50'%20cy%3D'50'%20r%3D'30'%20fill%3D'yellow'%20stroke%3D'xxx'%20stroke-width%3D'4'%2F%3E%3C%2Fsvg%3E

Note the stroke=xxx.  Firefox nightlies behave the same.

-- 
Cameron McCormack ≝ http://mcc.id.au/
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] Increasing the number of cross-platform/port expected results

[Cameron McCormack]

Dimitri Glazkov:
 I agree. We should organize cross-browser-test-fest and pick each
 other's brains.

I believe some Mozilla people are interested in working on a cross
browser test suite framework, based in part on reftests.  Jonathan Watt
and fantasai are people to coordinate with on this, IIRC.

-- 
Cameron McCormack ≝ http://mcc.id.au/
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] unwritten rules of webkit style

[Cameron McCormack]

David Levin:
 In copyright entries, don't use ranges for years. Use capital (C) for the
 copyright and no comma after the last year.  Example of a well formed
 copyright entry:
  * Copyright (C) 2004, 2005, 2006, 2007, 2008 Apple Inc. All rights
 reserved.

I’ve noticed a couple of different ways of writing subsequent copyright
lines, e.g.:

  Copyright (C) 2005 Somebody email
2006, 2007 Somebody Else email

  — http://trac.webkit.org/browser/trunk/WebCore/svg/SVGSVGElement.cpp

and:

  Copyright (C) 2005 Somebody email
  Copyright (C) 2006, 2007 Somebody Else email

  — http://trac.webkit.org/browser/trunk/WebCore/svg/SVGFilterElement.cpp

-- 
Cameron McCormack ≝ http://mcc.id.au/
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] Proposed Timer API

[Cameron McCormack]

Hi Maciej.

Cameron McCormack:
  If possible, it would be nice if there could be some degree of
  compatibility between this proposed API and the one in SVG Tiny 1.2:
 
   http://dev.w3.org/SVG/profiles/1.2T/publish/svgudom.html#svg__SVGTimer

Maciej Stachowiak:
 I considered that, but I don't like the fact that it makes the common  
 zero-delay continuation callback case into three lines of code instead  
 of one, for what I think is no practical benefit.

Justin’s proposed API seems to need four lines for that case:

  var t = new Timer();
  t.repeatCount = 1;
  t.addEventListener('timercomplete', function() { … }, false);
  t.start();

compared with the three for SVG’s timer:

  var t = createTimer(0, -1);
  t.addEventListener('SVGTimer', function() { … }, false);
  t.start();

Or do you mean compared to a simple function-like API, such as
setTimeout(), where it can be done in one line?  (Perhaps functions like
setHighResolution{Interval,Timeout}() would be easiest then.)

-- 
Cameron McCormack ≝ http://mcc.id.au/
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] High Resolution Timer API proposal(s)

[Cameron McCormack]

Maciej Stachowiak:
 I think I will mention some of these possible variations when  
 proposing the spec. At Hixie's suggestion I will propose it as a  
 standalone spec on [EMAIL PROTECTED], I recommend that those who  
 wish to follow the discussion subscribe to that list.

Hixie mentioned at one point that he’d like to see WindowTimers in a
separate spec, I think.  Now that there is the event loop stuff in
HTML 5 I don’t know whether that’s still his opinion, but if it is, will
you include setInterval()/setTimeout() in this Web Apps spec?  That
would be useful for SVG in the future.

Thanks,

Cameron

-- 
Cameron McCormack ≝ http://mcc.id.au/
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] Some Critical QtWebKit Doubts

[Cameron McCormack]

Benjamin Meyer:
 Those are not doubts, but questions.  Doubts are like:  I doubt you  
 have gone to the webkit wiki where there is a doc that while it  
 doesn't have much can get you started. 
 http://trac.webkit.org/wiki/QtWebKitHacking

Aside: using “doubt” to mean “question” is pretty standard Indian
English.

-- 
Cameron McCormack ≝ http://mcc.id.au/
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] whats bidi stand for?

[Cameron McCormack]

Hi Bin.

Bin Chen:
 I am reading the source code of webkit right now, I find a file name
 like bidi, I can't know the exact meaning, can you tell me whats this
 stand for?

“Bidi” is an abbreviation for “bidirectional text”, and refers to blocks
of text that use both left-to-right and right-to-left scripts (e.g. a
paragraph with English text that also includes some Arabic text).  See:

  http://en.wikipedia.org/wiki/Bi-directional_text

-- 
Cameron McCormack, http://mcc.id.au/
xmpp:[EMAIL PROTECTED]  ▪  ICQ 26955922  ▪  MSN [EMAIL PROTECTED]
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev