- New patterns/ directory with 7 initial failure-mode patterns (PAT-001..007) - skill-impact.md audit trail for skill modifications - _template.md for future pattern creation - index.md updated with Patterns section - log.md entry for this change - Inspired by arXiv:2608.27454 (WikiSkill)
2.1 KiB
2.1 KiB
pattern_id, title, category, severity, status, first_observed, last_updated, related_systems, related_solution_docs, related_skills
| pattern_id | title | category | severity | status | first_observed | last_updated | related_systems | related_solution_docs | related_skills | ||
|---|---|---|---|---|---|---|---|---|---|---|---|
| PAT-006 | LinkedIn login via browser — nativeInputSetter required, session expires between nav | integration | medium | active | 2026-07 | 2026-08-30 |
|
|
LinkedIn login via browser — nativeInputSetter required, session expires between nav
Symptom
Automated LinkedIn login via browser tools fails silently. Form fields appear filled but LinkedIn doesn't recognize the input (login button stays disabled, or submission fails with "invalid credentials").
Additionally, authenticated sessions expire between page navigations, requiring re-login on almost every navigation step.
Root Cause
-
React-controlled inputs: LinkedIn uses React, which manages input state internally. Simply setting
.valuevia DOM manipulation doesn't trigger React's onChange handler. ThenativeInputSetterapproach is required:const setter = Object.getOwnPropertyDescriptor( window.HTMLInputElement.prototype, 'value' ).set; setter.call(inputElement, 'my-value'); inputElement.dispatchEvent(new Event('input', { bubbles: true })); -
Session expiry: LinkedIn's SPA doesn't persist auth tokens reliably across
browser_navigatecalls (each navigation may reset the JS context).
Mitigation
- Always use
browser_consolewithnativeInputSetterfor form fills — NOTbrowser_clickfollowed by typing - Perform login + desired action in a SINGLE browsing session (minimize navigations)
- UTF-8 files must be saved without BOM (LinkedIn rejects BOM in posted content)
Prevention
- The
linkedin-personal-brandingskill documents this workflow - Never use
browser_clickfor LinkedIn form fields - Minimize navigation steps after login
Evidence
- Observed during LinkedIn branding sessions (Jul 2026)
- MEMORY.md entry: "Login via browser_console nativeInputSetter. NOT browser_click. Session expires between nav. UTF-8 no BOM."