Open
Bug 1333785
Opened 9 years ago
Updated 3 years ago
Form POST submission with a "_blank" target does not submit anything
Categories
(Firefox for iOS :: Browser, defect, P3)
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| fxios | + | --- |
People
(Reporter: adrien.joubert, Unassigned)
Details
(Whiteboard: [webcompat])
Attachments
(1 file)
|
481 bytes,
application/x-php
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36
Steps to reproduce:
As the summary says, when I am doing a post submission on a "_blank" targeted form which open a new tab, none input of the form are actually submitted to the server and I got no data on server side.
Here is (also attached with this ticket) a simple php page test I did set up to demonstrate it:
<html>
<body>
<?php
if( $_POST["name"] || $_POST["age"] ) {
echo "Welcome ". $_POST['name']. "<br />";
echo "You are ". $_POST['age']. " years old.";
exit();
}
?>
<form action = "<?php $_PHP_SELF ?>" method = "POST" target = "_blank">
Name: <input type = "text" name = "name" />
Age: <input type = "text" name = "age" />
<input type = "submit" />
</form>
</body>
</html>
Actual results:
The new opened tab doesn't get any of the submitted values.
Unlike any other browser as well as Android's Firefox browser version that actually do get values.
I also tested it with a different server app (java webapp).
Expected results:
I should except to see the submitted values into the new opened tab after the form has been submitted.
|
||
Updated•9 years ago
|
tracking-fxios:
--- → ?
|
||
Updated•9 years ago
|
|
|
||
Updated•9 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
|
||
Comment 1•6 years ago
|
||
Migrating Webcompat whiteboard priorities to project flags. See bug 1547409.
Webcompat Priority: --- → ?
|
|
||
Comment 2•6 years ago
|
||
See bug 1547409. Migrating whiteboard priority tags to program flags.
|
||
Updated•6 years ago
|
Webcompat Priority: ? → ---
|
||
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•