Freecodecamp: Waypoint: Create a Form Element - Make sure your form has an action attribute which is set to /submit-cat-photo.

[krispham]

I think I wrote correctly but it doesn't work like I thought :(

[ghost]

You have it correctly written i went back to mine and i had the same problem.

[bugron]

I am able to pass that test with your code. @krispham, @gwartney21 what OS and browser are you using?

[ghost]

@bugron I am using windows 10 and I am using Google Chrome for my browser

[tva10]

@bugron after adding example form in that task, there is an exception in conosle log (XSS Auditor....) I don't know why it is happens, but I pass this task near month ago.

[bugron]

@tva10 I can't replicate that in FF but in Chrome I can see that. I think this is caused by ?solution=.. part.

[zorfa]

I still have the same issue. I am unable to pass this test despite typing the right code. This problem only happens on Chrome browser in Windows 10.

[buiphuhai]

I have same problem. I cant pass through when typing this code in browser Google Chrome. Try Internet Explorer and pass it.

[zorfa]

I passed it using FireFox and it works. Is there any fix for chrome though?

[krispham]

@zorfa you was right, i change my browser and it works. @bugron What's wrong with Chrome :). But thanks you guys for help me.

[ltegman]

It looks like both this issue and #3636 are a duplicate of issue #3622

[ceautery]

I believe this is caused by a Chromium patch that addresses form actions: http://src.chromium.org/viewvc/blink?view=revision&revision=164538 which addresses this vulnerability report: https://code.google.com/p/chromium/issues/detail?id=331060

Essentially when the common framework script runs safeHTMLRun, preview.write will include a form with an action attribute, trigerring the XSS audit, replacing the action with "data:," in the iframe.

I don't see an obvious way to fix this eloquently, but you could fall back to having the test asserts check editor.getValue's content instead of the iframe DOM.

[hansinla]

I can confirm that on Mac OS X, Safari doesn't pas this test either. Firefox does.

[HunterJaffer]

If you're Mac then just do it on FireFox.

[giacarson]

Mac and Chrome/Safari - is this going to get fixed? I shouldn't have to install another browser for a bug :(

Edit: I did this on Firefox - it passed and continued but when I check my progress on the map back in Chrome it skips over those as being marked complete. So I'm not sure if that is going to count against my progress?

Edit 2: I finished the first section - it does not mark as complete.

[ceautery]

If no one is already working this, I can commit to starting a patch for it tonight.

[SaintPeter]

Not sure why the action attribute is getting overwritten:

[tnegherbon]

I've had the same problem on Chrome, but was able to validate on Edge.

[BerkeleyTrue]

@ceautery Thanks for relevant links. We assumed that Chrome did not like the form action in the URL. We will have to change these tests to against the editor value instead of loading in the iFrame. Unless someone can figure out how to write a form with an action in an iFrame without throwing the XSS auditor.

@bugron Do you have any ideas?

[ghost]

Same issue on Mac OS X and Chrome. Switched to FireFox and it worked. Although, shouldn't have to switch browsers to add a form element.

[BerkeleyTrue]

fix in the works

[jimmy0915]

Waypoint: Create a Form Element

[Homulvas]

I ran into this today using OS X Chrome and Safari. Should I create a new issue or can this one be reopened?

[AdamCEssmyer]

I can't get it to work in Firefox on OSX

[svt202]

Just had this same issue with Chrome/Windows 10. Internet explorer worked fine though!

[vladas1987]

you made syntax mistake:

should be:

[vladas1987]

you should use not these ' ' , but " "

[xiruim]

removed solution by mod

[IonZero1]

removed solution by mod

[AbidRiaz]

Worked for me. I wasn't using closing > for form element before

[EurekaPT]

I had the same problem. Solved with Opera browser. Thank you guys.

[dwaine619]

I just switched to incognito on chrome, and it worked!

[Neilfoster]

Same problem today, used firefox and it worked perfectly. Thanks