73 lines
28 KiB
JSON
73 lines
28 KiB
JSON
{
|
||
"task_intent": "Edit my post on Star Trek Starfleet Academy series by adding a line to the body that says \"Every watch makes me feel like a kid again\"",
|
||
"prompt": "# Instruction\n- You are an expert in cleaning process data descriptions. Given a task, you are provided with a set of annotation description\ndata for a certain visual LLM related to human user operation videos. Plus, You are provided with full trace of playwright action,\nwhic includes action and url before and after the action.\n- You need to analyze all the descriptive data and ultimately summarize a complete and reasonable user operation description that can accomplish the given task.\n- For each strategy, give a clear list of the low level action sequence.\n\n# Task\nEdit my post on Star Trek Starfleet Academy series by adding a line to the body that says \"Every watch makes me feel like a kid again\"\n\n# Annotation description\n## Part 1\n### Step-by-Step Actions in the Video Segment\n\n#### 1. **Action:** I click on the \"Subscribed\" tab.\n - **Page Changes:** The webpage updates to display a list of forum submissions under the \"Subscribed\" category. This includes various posts related to machine learning, each with details such as the title, submission date, and number of comments.\n - **Possible Purpose:** The likely intent is to view content from forums that I have subscribed to, focusing on topics of interest, particularly in the field of machine learning.\n\n#### 2. **Action:** I scroll down the page.\n - **Page Changes:** As I scroll, additional forum submissions become visible. The new entries continue the theme of machine learning, with titles indicating discussions on tools, papers, and projects related to the field.\n - **Possible Purpose:** The purpose of scrolling is to browse through more content within the subscribed forums, potentially looking for specific topics or recent updates.\n\n#### 3. **Action:** I click on the post titled \"[P] I made a command-line tool that explains your errors using ChatGPT (link in comments).\"\n - **Page Changes:** The webpage transitions to a detailed view of the selected post. This view includes the full text of the submission, any attached links or images, and a comment section where users have discussed the post. The specific post describes a command-line tool developed by the user, with further details available in the comments.\n - **Possible Purpose:** The action suggests an interest in learning more about this particular tool. By accessing the detailed view, I can read the full description, explore the provided link, and review the community's feedback and discussions related to the tool.\n\n#### 4. **Action:** I scroll through the comments section of the selected post.\n - **Page Changes:** Scrolling reveals multiple user comments, each providing feedback, questions, or additional information about the command-line tool. The comments are organized chronologically, with options to reply or upvote individual comments.\n - **Possible Purpose:** The intent behind this action is to gather more insights from the community's interaction with the post. Reading the comments can provide context, highlight potential issues or improvements, and offer a broader understanding of the tool's utility and reception.\n\n#### 5. **Action:** I return to the main \"Subscribed\" forum list.\n - **Page Changes:** The webpage reverts to the initial list of forum submissions under the \"Subscribed\" tab. The layout and content are consistent with the earlier view before selecting the specific post.\n - **Possible Purpose:** Returning to the main list allows me to continue exploring other topics or posts within the subscribed forums. This could be to find additional content of interest or to ensure I haven't missed any recent updates or discussions.\n\n### Summary\nIn this video segment, my actions focus on navigating and interacting with the \"Subscribed\" forum section. I begin by viewing the list of subscribed forum submissions, then select a specific post for detailed exploration, and finally return to the main forum list. Each step is aimed at engaging with relevant content, gathering detailed information, and maintaining an overview of ongoing discussions within the subscribed forums.\n\n---\n\n## Part 2\n### Step-by-Step Actions in the Video Segment\n\n#### 1. **Action:** I click on the \"Edit\" link next to the post titled \"Secret Invasion: Revealed: Inside Samuel L. Jackson's Eye-Opening New Marvel Series.\"\n - **Page Changes:** The page transitions to an editing interface for the selected post. This new interface includes fields for the URL, Title, and Body of the post, along with a preview section and submission buttons.\n - **Possible Purpose:** The likely intent is to modify the content of the existing post, possibly to update information, correct errors, or add new details.\n\n#### 2. **Action:** I click inside the \"Body\" text box.\n - **Page Changes:** The cursor appears in the \"Body\" text box, indicating that it is now active and ready for text input or editing.\n - **Possible Purpose:** The intention is to edit or add text to the body of the post. This could involve writing new content, making corrections, or formatting the existing text.\n\n#### 3. **Action:** I type the word \"Ever\" into the \"Body\" text box.\n - **Page Changes:** The word \"Ever\" appears in the \"Body\" text box, replacing or appending to any previous content.\n - **Possible Purpose:** The purpose is to begin drafting or updating the content of the post. Typing \"Ever\" might be the start of a sentence or a placeholder for further text.\n\n#### 4. **Action:** I click the \"Preview\" button below the \"Body\" text box.\n - **Page Changes:** A preview section appears, displaying how the post would look when published. The word \"Ever\" is shown in the preview, formatted according to the platform's display settings.\n - **Possible Purpose:** The intent is to see a visual representation of the post as it would appear to readers, allowing for final adjustments before submitting.\n\n#### 5. **Action:** I click the \"Edit submission\" button.\n - **Page Changes:** The page remains in the editing interface, but the action confirms the edits made to the post. No immediate visual change occurs other than the button interaction.\n - **Possible Purpose:** This action is likely a step toward saving the changes made to the post. It may also trigger a validation or confirmation process to ensure the edits are correctly applied.\n\n### Summary\nIn this video segment, I am engaged in editing a post on a forum or similar platform. I initiate the editing process by selecting the \"Edit\" option for a specific post, then proceed to modify the content within the \"Body\" text box. After typing new content, I preview the changes to assess the formatting and appearance. Finally, I confirm the edits by clicking the \"Edit submission\" button, preparing the post for submission or further review. Each step is focused on refining and updating the post content accurately.\n\n---\n\n## Part 3\n### Step-by-Step Actions in the Video Segment\n\n#### 1. **Action:** I click on the \"Edit submission\" button.\n - **Page Changes:** The webpage transitions to an editing interface where the submission details (URL, Title, Body) are now editable text fields.\n - **Possible Purpose:** The likely intent is to modify the existing submission, possibly to correct information, update content, or refine the wording.\n\n#### 2. **Action:** I click inside the \"Body\" text box.\n - **Page Changes:** The cursor appears within the \"Body\" text box, indicating it is active and ready for text input or editing.\n - **Possible Purpose:** The intention is to either add new text or edit the existing text within the \"Body\" section of the submission.\n\n#### 3. **Action:** I type the phrase \"Every watch makes me feel like a kid again\" into the \"Body\" text box.\n - **Page Changes:** The text \"Every watch makes me feel like a kid again\" appears in the \"Body\" text box, replacing or appending any previous content.\n - **Possible Purpose:** The purpose is to express a personal sentiment related to the submission topic, enhancing the submission with additional context or emotion.\n\n#### 4. **Action:** I click on the \"Preview Post\" button.\n - **Page Changes:** A preview section appears below the text box, displaying how the post will look once submitted. The typed phrase \"Every watch makes me feel like a kid again\" is shown in this preview.\n - **Possible Purpose:** The action aims to verify the formatting and appearance of the text before finalizing the submission, ensuring it meets the desired presentation.\n\n#### 5. **Action:** I click on the \"Edit submission\" button again.\n - **Page Changes:** The page remains in the editing mode, but this action might be a confirmation step or a preparation for further edits.\n - **Possible Purpose:** This could be a redundant click or an attempt to ensure that the submission is still in edit mode before proceeding with any additional changes.\n\n#### 6. **Action:** I click on the \"Post\" button.\n - **Page Changes:** A notification at the bottom of the page appears, stating \"The submission was edited,\" confirming that the changes have been saved.\n - **Possible Purpose:** The final intent is to save the edits made to the submission, updating the post with the new content in the \"Body\" section.\n\n### Summary\nIn this video segment, I am observed editing a submission on a website. The actions include entering edit mode, modifying the \"Body\" text, previewing the changes, and finally saving the edits. Each step is methodically performed to update the submission with a specific phrase, ensuring the changes are accurately reflected and saved.\n\n# Playwright action\n[\n {\n \"action_uid\": \"button_MarvelsGrantMan136\",\n \"idx\": 0,\n \"action_repr\": \"frame.clickget_by_role(\\\"button\\\", name=\\\"MarvelsGrantMan136\\\")\",\n \"before\": {\n \"url\": \"http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:9999/\"\n },\n \"after\": {\n \"url\": \"http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:9999/\"\n }\n },\n {\n \"action_uid\": \"link_Profile\",\n \"idx\": 1,\n \"action_repr\": \"frame.clickget_by_role(\\\"link\\\", name=\\\"Profile\\\")\",\n \"before\": {\n \"url\": \"http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:9999/\"\n },\n \"after\": {\n \"url\": \"http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:9999/\"\n }\n },\n {\n \"action_uid\": \"action_2\",\n \"idx\": 2,\n \"action_repr\": \"frame.clicklocator(\\\"article:nth-child(15) > .submission__row > .submission__inner > .submission__nav > .unlistify > li:nth-child(2) > .fg-inherit\\\")\",\n \"before\": {\n \"url\": \"http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:9999/f/television/135201/-/edit\"\n },\n \"after\": {\n \"url\": \"http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:9999/f/television/135201/-/edit\"\n }\n },\n {\n \"action_uid\": \"label_Body\",\n \"idx\": 3,\n \"action_repr\": \"frame.clickget_by_label(\\\"Body\\\")\",\n \"before\": {\n \"url\": \"http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:9999/f/television/135201/-/edit\"\n },\n \"after\": {\n \"url\": \"http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:9999/f/television/135201/-/edit\"\n }\n },\n {\n \"action_uid\": \"button_Edit submission\",\n \"idx\": 4,\n \"action_repr\": \"frame.clickget_by_role(\\\"button\\\", name=\\\"Edit submission\\\")\",\n \"before\": {\n \"url\": \"http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:9999/f/television/135201/-/edit\"\n },\n \"after\": {\n \"url\": \"http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:9999/f/television/135201/star-trek-starfleet-academy-series-from-alex-kurtzman-and\"\n }\n }\n]\n\n# Output format\n- 先总结整个任务的Objective，然后按照Strategy-SubStrategy-action三级层次来给出整个过程，\n- 接着给出整个操作流程后的观察和有趣的发现，最后严格按照json格式输出三级层次的过程描述。\n- 最后的输出json应该是包在```{json}```之间，最底层动作需要包含描述、对应的playwright动作指令顺序编号，以及具体指令内容。\n\n# Example\n### Complete User Operation Description to Display Labeled Issues in kkroening/ffmpeg-python\n\n**Objective:** Filter and display all issues labeled as \"question\" in the kkroening/ffmpeg-python repository.\n\n---\n\n#### **Strategy 1: Navigate to the Repository**\n**Low-Level Action Sequence:**\n1. **Search for the user \"kkroening\"**\n - Click the global search bar (placeholder: \"Search GitLab\").\n - Type \"kkroening\" and press `Enter`.\n2. **Select the user from results**\n - Click the \"Users\" tab in search results.\n - Click on \"Karl Kroening @kkroening\" in the user list.\n3. **Access the repository**\n - Navigate to the \"Personal projects\" section.\n - Click on the \"ffmpeg-python\" project.\n\n---\n\n#### **Strategy 2: Filter Issues by Label**\n**Low-Level Action Sequence:**\n1. **Open the Issues tab**\n - Scroll to the left sidebar menu.\n - Click the \"Issues\" tab (displaying the count, e.g., \"Issues 402\").\n2. **Apply label filtering**\n - Click the search/filter bar in the issues list.\n - Select the \"Label\" dropdown from the filter options.\n - Type or select \"question\" from the label dropdown.\n - Click the search/apply button to confirm the filter.\n\n---\n\n#### **Final Oberservation**\nThe issues list will refresh to show only issues with the \"question\" label. The URL will reflect the filter:\n`.../ffmpeg-python/-/issues/?label_name[]=question`.\n\n---\n\n### Key Observations from Playwright Trace\n- The final URL after filtering:\n `http://ec2-3-135-39-80.../ffmpeg-python/-/issues/?label_name%5B%5D=question`\n confirms the \"question\" label filter is applied.\n- Critical interactions include selecting the \"Label\" dropdown and explicitly choosing \"question\" to refine results.\n\n### Final output\n```json\n[{\n \"strategy\" : \"Navigate to the Repository\",\n \"substrategies\": [\n {\n \"substrategy\": \"Search for the user \\\"kkroening\\\"\",\n \"actions\" : [\n {\n \"description\": \"Click the global search bar (placeholder: \\\"Search GitLab\\\"). \",\n \"playwright_idx\" : 18,\n \"playwright_instruction\" : \"frame.pressget_by_placeholder(\\\"Search GitLab\\\")Enter\"\n }\n ]\n },\n {\n \"substrategy\": \"Select the user from results\",\n \"actions\" : [\n ]\n }\n ]\n},\n{\n \"strategy\" : \"Filter Issues by Label\",\n \"substrategies\" : [\n ]\n}]\n```",
|
||
"response": "<think>\nOkay, let's tackle this problem. The user wants to edit their post on the Star Trek Starfleet Academy series by adding a specific line to the body. The task is to analyze the provided annotation descriptions and playwright actions to create a step-by-step process.\n\nFirst, I need to look at the three parts of the annotation descriptions. Part 1 seems to be about navigating the Subscribed tab and selecting a post. Part 2 and Part 3 involve editing a post, adding text to the body, previewing, and submitting. The Playwright actions include clicking on buttons and links related to editing the submission.\n\nWait, the task is to add a line to the body. So the main steps would involve accessing the edit page of the specific post, modifying the body, adding the required line, previewing, and then saving the changes.\n\nLooking at Part 3, the user types \"Every watch makes me feel like a kid again\" into the Body text box. That's exactly what the task requires. But there's also a mention of clicking the 'Edit' link in Part 2. So combining these steps.\n\nThe Playwright actions show a sequence: clicking on a button named \"MarvelsGrantMan136\", then a link, then editing the submission, clicking the Body label, and finally clicking the \"Edit submission\" button. The URLs change from the edit page back to the post after submission.\n\nPutting this together, the strategies would be:\n\n1. Navigate to the user's profile to access their posts. The Playwright actions start with clicking on the user's button and the Profile link. This is probably how the user gets to their own posts.\n\n2. Locate and enter edit mode for the specific post. The Playwright action 2 is clicking on the edit link of the post (article nth-child(15), etc.), which takes them to the edit page.\n\n3. Modify the post body by adding the new line. This involves clicking the Body field, typing the line, previewing, and submitting. The Playwright actions 3 and 4 correspond to clicking the Body label and then the Edit submission button.\n\nWait, in the Playwright actions, after clicking the Body label (action_uid: label_Body, idx 3), then action_uid: button_Edit submission (idx 4) is clicked, which takes the URL back to the post. So that's the final submission.\n\nBut in the annotations, Part 3 mentions clicking the \"Post\" button which triggers a notification. However, in the Playwright trace, the last action is clicking \"Edit submission\" which might be the save button. There's a discrepancy here. Maybe the \"Edit submission\" button in the Playwright actions is actually the submit button after editing.\n\nSo the steps would be:\n\n- Navigate to Profile to find the post.\n- Click Edit on the specific post.\n- Edit the Body by adding the line.\n- Preview and submit the changes.\n\nNow, mapping the strategies:\n\nStrategy 1: Access User Profile to Locate Post. Substrategies: Navigate to profile, find the post.\n\nStrategy 2: Enter Post Editing Mode. Click the Edit link.\n\nStrategy 3: Edit Post Body. Add the line, preview, submit.\n\nLooking at the Playwright actions:\n\nThe first two actions are on the main page, clicking the user button and Profile link. Then action 2 is clicking the edit link (article nth-child(15)...), which takes them to the edit URL. Then clicking the Body label (action 3), then clicking the Edit submission button (action 4), which navigates back to the post URL.\n\nSo the steps in Playwright are:\n\n0. Click user button (MarvelsGrantMan136)\n1. Click Profile link\n2. Click Edit link on the post (action_uid: action_2)\n3. Click Body label (action_uid: label_Body)\n4. Click Edit submission button (action_uid: button_Edit submission)\n\nBut in the annotations, Part 3 includes typing the phrase and previewing. However, the Playwright actions don't show typing or previewing steps. This might be because Playwright traces only capture the navigation and clicks, not text input. So the annotations include steps that are user inputs (typing) which aren't captured in Playwright actions, but the Playwright actions only show the clicks and navigation.\n\nTherefore, the final process should combine both the annotation steps and the Playwright actions. The key is to map the annotation steps to the Playwright actions where possible.\n\nSo the strategies would be:\n\n1. Navigate to the User's Profile to Access Submissions\n - Click on the user's profile button (Playwright action 0)\n - Click on the \"Profile\" link (Playwright action 1)\n\n2. Enter Edit Mode for the Target Post\n - Locate the post titled \"Star Trek Starfleet Academy series\" and click its \"Edit\" link (Playwright action 2)\n\n3. Modify the Post Body with the New Line\n - Click into the \"Body\" text box (Playwright action 3)\n - Type the new line \"Every watch makes me feel like a kid again\"\n - Click \"Preview Post\" to verify (not in Playwright actions, but from annotations)\n - Click \"Edit submission\" button to save (Playwright action 4)\n\nWait, in the Playwright actions, after clicking the Body label (action 3), then action 4 is clicking the \"Edit submission\" button. But according to the annotations, after typing, they click Preview and then Post. But in the Playwright trace, the final action is clicking \"Edit submission\" which navigates back to the post URL. So perhaps the \"Edit submission\" button is the one that saves the changes. Maybe the \"Post\" button in the annotations is the same as the \"Edit submission\" button in Playwright.\n\nSo the steps would be:\n\nAfter editing the body and previewing, clicking the \"Edit submission\" button saves the changes, which is action 4 in Playwright.\n\nSo the final JSON should map each action to the Playwright steps where applicable. The typing and preview steps are part of the annotation but not in Playwright actions, so those steps would have playwright_idx as null or not present. But according to the example, the actions need to include playwright_idx and instruction if applicable.\n\nBut in the example, some actions have playwright_idx. So for steps that are captured in Playwright actions, we include their idx and instruction. For steps like typing or previewing, which are not in Playwright trace, we might omit those fields or set them to null. However, the user's output example includes actions without playwright_idx. Wait, looking at the example, some actions have playwright_idx and playwright_instruction, others don't. So perhaps only include those that are present in the Playwright trace.\n\nIn the given problem, the typing and preview steps are in the annotations but not in the Playwright actions. So in the JSON output, those steps would not have playwright_idx or instruction. But according to the problem statement, the final json should include the playwright action sequence numbers and instructions for the lowest level actions. So, the steps that correspond to Playwright actions should have their idx and instruction.\n\nSo, for example, clicking the \"Edit\" link is Playwright action 2, clicking the Body is action 3, and clicking the Edit submission button is action 4. The typing and preview steps are not in Playwright actions, so they don't have those fields.\n\nTherefore, the JSON structure would have strategies and substrategies, with actions that include the description and, where applicable, the playwright info.\n\nPutting it all together:\n\nObjective: Edit the post titled \"Star Trek Starfleet Academy series\" by adding the line \"Every watch makes me feel like a kid again\" to the body.\n\nStrategy 1: Navigate to User Profile to Access Submissions\n- Substrategy: Access Profile\n - Click user profile button (Playwright action 0)\n - Click Profile link (Playwright action 1)\n\nStrategy 2: Enter Edit Mode for the Target Post\n- Substrategy: Locate and Edit Post\n - Click Edit link on the specific post (Playwright action 2)\n\nStrategy 3: Modify Post Body and Submit Changes\n- Substrategy: Edit Body Content\n - Click Body text box (Playwright action 3)\n - Type the new line (no Playwright action)\n - Preview the changes (no Playwright action)\n- Substrategy: Finalize Edits\n - Click Edit submission button (Playwright action 4)\n\nThe final JSON would map these steps, including the Playwright actions where applicable. The typing and preview steps are part of the process but not captured in Playwright, so they are included as actions without playwright data.\n\nKey observations: The final URL after submission returns to the post, confirming the edit was saved. The Playwright trace shows the navigation from edit page back to the post URL after clicking the submission button.\n</think>\n\n```json\n[\n {\n \"strategy\": \"Navigate to User Profile to Access Submissions\",\n \"substrategies\": [\n {\n \"substrategy\": \"Access Profile Page\",\n \"actions\": [\n {\n \"description\": \"Click on the user profile button (MarvelsGrantMan136).\",\n \"playwright_idx\": 0,\n \"playwright_instruction\": \"frame.clickget_by_role(\\\"button\\\", name=\\\"MarvelsGrantMan136\\\")\"\n },\n {\n \"description\": \"Click the \\\"Profile\\\" link to view user submissions.\",\n \"playwright_idx\": 1,\n \"playwright_instruction\": \"frame.clickget_by_role(\\\"link\\\", name=\\\"Profile\\\")\"\n }\n ]\n }\n ]\n },\n {\n \"strategy\": \"Enter Edit Mode for the Target Post\",\n \"substrategies\": [\n {\n \"substrategy\": \"Locate and Initiate Post Editing\",\n \"actions\": [\n {\n \"description\": \"Click the \\\"Edit\\\" link for the post titled \\\"Star Trek Starfleet Academy series\\\".\",\n \"playwright_idx\": 2,\n \"playwright_instruction\": \"frame.clicklocator(\\\"article:nth-child(15) > .submission__row > .submission__inner > .submission__nav > .unlistify > li:nth-child(2) > .fg-inherit\\\")\"\n }\n ]\n }\n ]\n },\n {\n \"strategy\": \"Modify Post Body and Submit Changes\",\n \"substrategies\": [\n {\n \"substrategy\": \"Edit Body Content\",\n \"actions\": [\n {\n \"description\": \"Click inside the \\\"Body\\\" text box to activate it.\",\n \"playwright_idx\": 3,\n \"playwright_instruction\": \"frame.clickget_by_label(\\\"Body\\\")\"\n },\n {\n \"description\": \"Type the phrase \\\"Every watch makes me feel like a kid again\\\" into the \\\"Body\\\" text box.\"\n },\n {\n \"description\": \"Click the \\\"Preview Post\\\" button to verify formatting.\"\n }\n ]\n },\n {\n \"substrategy\": \"Finalize Edits\",\n \"actions\": [\n {\n \"description\": \"Click the \\\"Edit submission\\\" button to save changes.\",\n \"playwright_idx\": 4,\n \"playwright_instruction\": \"frame.clickget_by_role(\\\"button\\\", name=\\\"Edit submission\\\")\"\n }\n ]\n }\n ]\n }\n]\n```",
|
||
"final_output": [
|
||
{
|
||
"strategy": "Navigate to User Profile to Access Submissions",
|
||
"substrategies": [
|
||
{
|
||
"substrategy": "Access Profile Page",
|
||
"actions": [
|
||
{
|
||
"description": "Click on the user profile button (MarvelsGrantMan136).",
|
||
"playwright_idx": 0,
|
||
"playwright_instruction": "frame.clickget_by_role(\"button\", name=\"MarvelsGrantMan136\")"
|
||
},
|
||
{
|
||
"description": "Click the \"Profile\" link to view user submissions.",
|
||
"playwright_idx": 1,
|
||
"playwright_instruction": "frame.clickget_by_role(\"link\", name=\"Profile\")"
|
||
}
|
||
]
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"strategy": "Enter Edit Mode for the Target Post",
|
||
"substrategies": [
|
||
{
|
||
"substrategy": "Locate and Initiate Post Editing",
|
||
"actions": [
|
||
{
|
||
"description": "Click the \"Edit\" link for the post titled \"Star Trek Starfleet Academy series\".",
|
||
"playwright_idx": 2,
|
||
"playwright_instruction": "frame.clicklocator(\"article:nth-child(15) > .submission__row > .submission__inner > .submission__nav > .unlistify > li:nth-child(2) > .fg-inherit\")"
|
||
}
|
||
]
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"strategy": "Modify Post Body and Submit Changes",
|
||
"substrategies": [
|
||
{
|
||
"substrategy": "Edit Body Content",
|
||
"actions": [
|
||
{
|
||
"description": "Click inside the \"Body\" text box to activate it.",
|
||
"playwright_idx": 3,
|
||
"playwright_instruction": "frame.clickget_by_label(\"Body\")"
|
||
},
|
||
{
|
||
"description": "Type the phrase \"Every watch makes me feel like a kid again\" into the \"Body\" text box."
|
||
},
|
||
{
|
||
"description": "Click the \"Preview Post\" button to verify formatting."
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"substrategy": "Finalize Edits",
|
||
"actions": [
|
||
{
|
||
"description": "Click the \"Edit submission\" button to save changes.",
|
||
"playwright_idx": 4,
|
||
"playwright_instruction": "frame.clickget_by_role(\"button\", name=\"Edit submission\")"
|
||
}
|
||
]
|
||
}
|
||
]
|
||
}
|
||
]
|
||
} |