EXPECT_EQ(u"__gCrWeb.callFunctionInGcrWeb('autofill', 'fillForm', "All fields are sent and we also added the isAutofilled data.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
add a bit more details of this involves
my understanding is that we now allow filling empty filldata and unmark autofilled in the renderer
EXPECT_EQ(u"__gCrWeb.callFunctionInGcrWeb('autofill', 'fillForm', "All fields are sent and we also added the isAutofilled data.
ok so we only added isAutofilled to the fill call args basically ?
secondFieldData.Set("isAutofilled", YES);do we have a test case for validating the behavior when isAutofilled is NO ?
@"document.getElementById('email')."
@"hasAttribute('chrome-autofilled');",is this attr set async after FillForm() is done (when `block_was_called` == true) ?
otherwise you dont need to wait
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
add a bit more details of this involves
my understanding is that we now allow filling empty filldata and unmark autofilled in the renderer
Done
EXPECT_EQ(u"__gCrWeb.callFunctionInGcrWeb('autofill', 'fillForm', "Vincent BoisselleAll fields are sent and we also added the isAutofilled data.
ok so we only added isAutofilled to the fill call args basically ?
Yes and since we are not skipping empty fields and `autofilled == false` anymore, field 4 and 5 are added to the expected result.
@"document.getElementById('email')."
@"hasAttribute('chrome-autofilled');",is this attr set async after FillForm() is done (when `block_was_called` == true) ?
otherwise you dont need to wait
Without the wait the test was failing since the attribute is added in a window.setTimeOut.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
@"document.getElementById('email')."
@"hasAttribute('chrome-autofilled');",Jean-François Leis this attr set async after FillForm() is done (when `block_was_called` == true) ?
otherwise you dont need to wait
Without the wait the test was failing since the attribute is added in a window.setTimeOut.
ah! I forgot about that
fillign results are returned but there is still that timeout before it actually happens
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
EXPECT_EQ(u"__gCrWeb.callFunctionInGcrWeb('autofill', 'fillForm', "Vincent BoisselleAll fields are sent and we also added the isAutofilled data.
Jean-François Leok so we only added isAutofilled to the fill call args basically ?
Yes and since we are not skipping empty fields and `autofilled == false` anymore, field 4 and 5 are added to the expected result.
Done
do we have a test case for validating the behavior when isAutofilled is NO ?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
undoFirstFieldData.Set("isAutofilled", NO);curious, what happens when we undo autofills that are stacked ?
is `isAutofilled` going to be kept if we undo to another previous fill
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |