Update FAQ to clarify string field ordering in browser integration

[Copilot]

The FAQ section "How do I fill in additional values on a webpage?" contained misleading information about the order of KPH attributes being "critical" when setting up string fields for browser integration.

Changes Made

• Removed misleading information: Eliminated the incorrect statement that "the order is critical" when creating KPH attributes
• Added proper reference: Included a link to the comprehensive KeePassXC-Browser Wiki for detailed instructions
• Clarified alphabetical ordering: Explained that string fields are numbered based on alphabetical order of KPH attributes, not creation order
• Simplified instructions: Streamlined the quick overview to focus on essential steps without confusing examples

Why This Matters

Users were confused because the advanced attributes in KeePassXC are automatically sorted alphabetically, which contradicted the FAQ's claim that order matters. This led to uncertainty about whether the feature was broken or if the documentation was incorrect.

The updated FAQ now accurately reflects how KeePassXC-Browser actually works:

• String Field #1 corresponds to the first KPH attribute in alphabetical order
• String Field #2 corresponds to the second KPH attribute in alphabetical order
• The names after "KPH: " are just for user reference and don't affect functionality

Fixes #162.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[cloudflare-workers-and-pages[bot]]

Deploying keepassxc-org with    Cloudflare Pages

Latest commit:	522eded
Status:	🚫  Build failed.

View logs