IE浏览器VBScript表单自动填充代码失效问题求助

各位晚上好，我在测试一个HTML页面的自动化功能时遇到问题，尝试用VBScript实现表单字段自动填充，该页面包含一个输入字段和提交按钮。

输入字段代码如下：

<input ng-reflect-id="firstName" id="firstName" ng-reflect-type="text" type="text" ng-reflect-placeholder="Legal Name" placeholder="name" class="ng-pristine ng-valid ng-touched">

提交按钮代码如下：

<button ng-reflect-type="submit" type="submit" ng-reflect-id="next_btn" id="next_btn" ng-reflect-class-name="btn mobile-primary margin-bottom-15" class="btn mobile-primary margin-bottom-15"> Register </button>

我的VBScript代码如下：

On Error Resume Next 
Const PAGE_LOADED = 4 
Set objIE = CreateObject("InternetExplorer.Application") 
Call objIE.Navigate("my page URL") 
objIE.Visible = True 
Do Until objIE.ReadyState = PAGE_LOADED : Call WScript.Sleep(100) : Loop 
objIE.Document.all.Item("firstName").Value = "Test" 
call objIE.Document.all.Item("next_btn").click 
Set objIE = Nothing

恳请告知这段代码无法正常运行的原因。

Hey there, let's break down why your script isn't working—this is a super common pain point with Angular-powered pages, since they load content dynamically even after the browser says it's "done". Here are the key issues and fixes:

1. ReadyState = 4 doesn't mean Angular is finished rendering #

The browser's ReadyState = 4 only tells you the static HTML has loaded, but Angular takes extra time to initialize components, bind data, and make elements fully interactive. Your script is trying to interact with elements that might exist in the DOM but aren't actually ready for input yet.

2. On Error Resume Next is hiding real errors #

This line squashes all error messages, so you can't tell if the script is failing to find the element, if the element is unresponsive, or something else entirely. Remove it temporarily to see the exact error (like "Object required")—that will point you straight to the problem.

3. Document.all.Item is an outdated way to grab elements #

While it works in some cases, using getElementById is more reliable and standard for targeting elements by their id attribute. It's less prone to unexpected behavior than the older Document.all collection.

Fixed Script Example #

Here's a revised version that waits explicitly for elements to be available, uses proper element selection, and removes error suppression so you can debug easily:

Const PAGE_LOADED = 4 
Set objIE = CreateObject("InternetExplorer.Application") 
objIE.Navigate("my page URL") 
objIE.Visible = True 

WaitForPageLoad objIE
WaitForElement objIE, "firstName"
WaitForElement objIE, "next_btn"

' Fill the input and click the button
objIE.Document.getElementById("firstName").Value = "Test"
objIE.Document.getElementById("next_btn").Click

Set objIE = Nothing

' Helper function to wait for page to fully load
Sub WaitForPageLoad(ie)
    Do Until ie.ReadyState = PAGE_LOADED And Not ie.Busy
        WScript.Sleep 100
    Loop
End Sub

' Helper function to wait until an element exists in the DOM
Sub WaitForElement(ie, elementId)
    Dim elem
    Set elem = Nothing
    Do While elem Is Nothing
        On Error Resume Next ' Only suppress error here to check element existence
        Set elem = ie.Document.getElementById(elementId)
        On Error Goto 0 ' Turn error handling back on immediately
        WScript.Sleep 200
    Loop
End Sub

Why this works: #

• The WaitForElement loop keeps checking until the element is actually present and accessible, not just loaded in the static HTML.
• We added a check for ie.Busy in WaitForPageLoad to make sure the browser isn't still fetching resources in the background.
• Using getElementById is more direct and less likely to run into edge cases than Document.all.Item.

If you still hit issues, try increasing the sleep time in WaitForElement—some Angular apps take longer to render components depending on network speed or app complexity.

内容的提问来源于stack exchange，提问作者NICK