Jump to content
Search Community

Client-side Issue

dada78 test
Moderator Tag

Go to solution Solved by GreenSock,

Warning: Please note

This thread was started before GSAP 3 was released. Some information, especially the syntax, may be out of date for GSAP 3. Please see the GSAP 3 migration guide and release notes for more information about how to update the code to GSAP 3's syntax. 

Recommended Posts

Hi guys,

I am on a banner project where the client is serving their own banners.

 

The requirements are that everything is being included in one html file and that no external calls are allowed. I included some of your fantastic minified libraries into the html file and the banner keep getting rejected by their QA, because apparently there is an external call to "http://www.w3.org/1999/xhtml" in the html (which is just a reference as part of the libs), not an active call to an external URL. When checking with dev tools, no such call exists.

 

Sounds like to me they are running it through some validator that looks for URLs in the code and then flags them...

 

Anyone else running into this issue?

 

Thanks!

Link to comment
Share on other sites

Hello dada78

 

Depending where it is you might be able to remove it

 

What tag is that "http://www.w3.org/1999/xhtml" on? If it is on the html tag as a xmlns attribute you can remove it. But if that is the case that mean you might be using a XHTML doctype instead of html5 standards doc type.

 

Usually with HTM5 page and doctype the page would look like this before anything added to it.

<!doctype html>
<html>
<head>
<meta charset="utf-8">
<title>Untitled Document</title>
</head>
<body>
</body>
</html>

If your not using a html5 doctype then are you using XHTML transitional doctype ?

 

Any additional info would be highly appreciated :)

Link to comment
Share on other sites

  • Solution

Jonathan is right - that is just a namespace URL that has nothing to do with any outside calls. It sounds like whatever system they're using to sense external calls is flawed. Maybe they don't deal with SVG much? Hopefully you can just tell them about it being a namespace thing and that GSAP has made it through the rigorous vetting by Google and every major ad network. Ideally they'd just let it be and not make you edit the files. 

  • Like 2
Link to comment
Share on other sites

Hey guys,

so we just got off a call with the client and they are insisting on removing the namespace (even though it doesn't load anything! argh...). Very frustrating. So my next question would be: Would it be possible to remove these 2 mentions from the GSAP CSS plugin without breaking anything?

 

Thanks!

--------------------------
Update: HA, the client changed their minds (halleluja). That was a very long and painful birth...

  • Like 4
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...