Minutes, 28 July 2016 SVG WG telcon

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Minutes, 28 July 2016 SVG WG telcon

Nikos Andronikos


      [1] http://www.w3.org/

                               - DRAFT -

                    SVG Working Group Teleconference

28 Jul 2016


      [2] https://lists.w3.org/Archives/Public/www-svg/2016Jul/0012.html

   See also: [3]IRC log

      [3] http://www.w3.org/2016/07/28-svg-irc


          Tav, nikos, stakagi, shepazu, AmeliaBR




     * [4]Topics
         1. [5]SVG 2 publication
         2. [6]SVG website
     * [7]Summary of Action Items
     * [8]Summary of Resolutions

   <scribe> scribe: Nikos

   <scribe> scribenick: nikos

SVG 2 publication

   shepazu: I'll have the references replaced by Sunday night

   nikos: I was going to start publication on Monday so that's

   <AmeliaBR> [9]https://github.com/w3c/svgwg/milestone/1

      [9] https://github.com/w3c/svgwg/milestone/1

   nikos: I was just looking at whether we can close the one about
   transform on textpath

   AmeliaBR: Think the only bit that wasn't addressed is if
   there's a transform on the path itself
   ... think we should go with firefox/chrome

   shepazu: we'll need to schedule a CR transition
   ... we'll need to get PLH to come on a call with us
   ... someone else who takes the role of director will join
   ... we'll look at our comments. We'll probably need to do a
   disposition of comments
   ... I'll see what the current practice via github is
   ... we'll have to say that we've paid attention to and
   addressed all the issues - could be a spec change, could be no
   change, etc
   ... everything that we haven't resolved. We should mark as next

SVG website


     [10] https://www.w3.org/Graphics/SVG/feedback.html

   nikos: Needs updating. Assume there's some vcs archive

   <AmeliaBR> The "SVG 2" Github label is now "SVG Core"

   shepazu: Just send me what you think should be on there
   ... I can set up a redirect to a wiki page

   <shepazu> [11]http://www.specref.org/?q=CSS%20VALUES

     [11] http://www.specref.org/?q=CSS VALUES

   <AmeliaBR> The "CR 2" Github milestone is now "SVG Core

   <AmeliaBR> [12]https://github.com/w3c/svgwg/milestone/1

     [12] https://github.com/w3c/svgwg/milestone/1

   nikos: Of the remaining open isses
   ... equivalent transform is wrong - I did that last night and
   just need to edit and close issue
   ... disallow transforms on textPath is done, just need to file
   bug on css and close issue
   ... for updateNumberOfChars, the question is whether
   display:none has the same effect as visibility
   ... propose display:none inline elements aren't counted,
   visibility:hidden does count

   Tav: I disagree. If you use dx,dy

   shepazu: one reason people want this is because they don't have
   text wrapping, they have to do it manually

   Tav: Don't think this is a huge issue

   AmeliaBR: we're conflicted, implementations are conflicted.
   Let's go with the majority of implementations

   shepazu: I agree

   nikos: Think we spec and file a FireFox bug, if they don't
   agree that will start conversation

   RESOLUTION: getNumberOfChars will not count display:none chars
   (Issue #200)

   nikos: Next is update vector-effects options being marked as

   AmeliaBR: I'll do that

   nikos: Next is review content model on all elements.
   ... I'm pretty happy that won't require changes. We've had a
   lot of review from non members.
   ... That's all of them

   trackbot, end telcon


     [13] http://w3c.github.io/workshops/blockchain/graphics/01_W3C_Opening.svg

Summary of Action Items

Summary of Resolutions

    1. [14]getNumberOfChars will not count display:none chars
       (Issue #200)

   [End of minutes]

The information contained in this email message and any attachments may be confidential and may also be the subject to legal professional privilege. If you are not the intended recipient, any use, interference with, disclosure or copying of this material is unauthorised and prohibited. If you have received this email in error, please immediately advise the sender by return email and delete the information from your system.