From the update I get this error how I can repair it "TypeError: a.getTransformToElement is not a function"

[valki...@gmail.com]

This message appears when I try to open any of the files I had already created with the previous version of the web designer.

"No se puede abrir D:\####\index.html debido al siguiente error: TypeError: a.getTransformToElement is not a function."

How can I fix it to continue working on them ???

[Sukhbir Kaur]

Hi,

Can you please send us one of your files (Pre-published) @gwd-s...@google.com which was working in the previous version so we can debug it .

Thanks

Sukhbir

(Google Web Designer Team)

[Zachary Yaro]

Is there any fix you can recommend in the meantime?  The bug does not seem to affect all Google Web Designer files, but a lot of our GWD files can only be opened by people who held off on updating to version 1.7.

If there is no fix, is there a way to revert to an earlier version of GWD until the problem is solved?

Thank you,

Zachary Yaro

[Nivesh Rajbhandari]

Hi,

The new version of Chromium that GWD uses does not support embedded SVG because an API we rely on has been deprecated - https://bugs.chromium.org/p/chromium/issues/detail?id=231609.

Per our release notes:

Changes to SVG editing

• Double clicking on an SVG image no longer goes in editing mode.

When you import SVG files, they are added to your HTML using an IMG element that references the .svg file. However, it seems some users have embedded SVG content that they hand-coded in Code view.

As a workaround, please try the following:

1. Open your index.html file in a text editor
2. For each <svg> ... </svg> element, cut and paste the entire element into a text file and save it as an .svg file inside your assets folder.
3. In place of the <svg> ... </svg> element, replace it with an IMG element, something like:
   
   <img is="gwd-image"source="assets/mySvgFile1.svg" >
   
   (This example is for an Ads file that has pages.)
   
   If you are working on non-pages based HTML files, you would do something like:
   
   <img src="assets/mySvgFile.svg" >
   
   
4. You may also want to update the 'id' and 'class' attributes if needed.

For example, if your file had an embedded SVG element like:

<svg id="mycircle" class="gwd-div-abc" width="100" height="100">
  <circle cx="50" cy="50" r="40" stroke="green" stroke-width="4" fill="yellow" />
</svg>

You would copy it to a new text file named circle.svg and save this file in your assets folder next to your index.html file. If the id and class attributes are used in other parts of GWD, you would remove them from the .svg file and transfer them to the <img> element that replaces the <svg> tag, as in:

<img is="gwd-image" source="assets/circle.svg" id="mycircle" class="gwd-div-abcd">

The assets/circle.svg file contains:

<svg width="100" height="100">
  <circle cx="50" cy="50" r="40" stroke="green" stroke-width="4" fill="yellow" />
</svg>

If you are working on an HTML file (without pages), you would use an IMG element and a 'src' attribute as in:

<img src="assets/circle.svg" id="mycircle" class="gwd-div-abcd">

We hope this helps you get back to working with your files.

Thanks!

[Zachary Yaro]

We used embedded <svg>s for several things that cannot be done using <img>s, such as allowing colors to be changed in response to user actions.  Will embedded <svg>s be supported in a future release, or must we rewrite our past work to use GWD 1.7.  If the latter, is there a way to revert to a previous version?

Thank you,

Zachary Yaro

[nestorc...@gmail.com]

Alguien tiene la solución para este problema. Me sucede lo mismo que Zachary Yaro. Saludos

[Glennise Pascua]

Hi Nivesh,

Would it be possible to dynamically change css styles (border, color) for SVG elment inside <img> upon user interaction? Can you provide insights on how to achieve this?

Thanks!

[valki...@gmail.com]

I think if you load a svg with the <img> tags you lose all those possibilities or try jquerys

[Neil G]

My creative needs to use inline svg so I can change the properties of the image in real-time. I need to make an amendment to the creative and can no longer open it in GWD causing me a lot of issues. This is very frustrating and is not the first time GWD has made changes that render previous builds useless. I either need a way to role back to a previous version of GWD that does work or a workaround to use inline svg. At the very least there should be backward compatibility with older files (though my creative isn't even old). 

Is the removal of features without any consideration to how it affects existing builds going to be common? If it is then I will have to change my recommendations to the business to use GWD as a primary tool for HTML5 ads. It isn't feasibile to have to rebuild creative all the time.

[San Khong]

Hi Neil,

I'm sorry you're running into this issue.  It seems like it's a bug and not because of the removal of features.  Can you please send us the file so we can make sure it will be fixed properly?  Please send it to gwd-s...@google.com

San

Google Web Designer team

[Neil G]

Hi San,

I sent everything off as requested. Are there any updates on this bug? I'm still having to make edits in the complied version of my creative, which is not ideal.

 

[San Khong]

Hi Neil,

Your email did not go through my inbox but I found your file in the internal gwd-support groups.  I will get back to you soon on this!  Sorry about this.

San

[San Khong]

Hi Neil,

The support for inline svg will be fixed in the next major release (around May).  I've looked at the file and found no workaround except for using image which is not something you want. I've also tried to see if we can release the fix now but due to the complication of the fix to support inline svg, it's not possible to do a dot release because of the many changes involved.  I'm so sorry.

[dec...@in-queue.com]

I'm receiving this error when I try to reopen a file I worked on previously.

TypeError: a.getTransformToElement is not a function

The file will not open in GWD.

HTML files are attached. I can send support files if needed

[San Khong]

Hi all,

This should be fixed in the latest release 1.8.0.0503.  Please let us know if you still run into issues.

Thanks,