secondlife / secondlife/viewer

Add LEAP API for querying embedded browser/media content

Open
#5,682 2 comments 0 reactions 1 assignee View on GitHub

@maxim-productengine is already working on this.

Since Apr 21, 2026.

  • #5754 by @maxim-productengine — merged
enhancement LEAP_additions qa:automation
Dominant language
C++
Stars
299
Forks
146
Avg merge
1d 9h
Merged PRs (30d)
88

Description

Summary

The LEAP API currently has no way to inspect or interact with embedded browser (<web_browser>) content within the viewer. This limits test automation for any feature that relies on web content rendered inside the viewer, such as the login splash page (login_html).

Current Behavior

  • LEAP can query the <web_browser> widget's existence, visibility, and rectangle via the UI API
  • There is no API to access:
    • The current URL loaded in the browser
    • The page's DOM or text content
    • Navigation state (loading, loaded, error)
    • Page title

Desired Behavior

A LEAP API (e.g., LLMediaAPI or extension of the existing LLViewerWindowAPI) that supports:

  1. getMediaInfo(path) — Returns the current URL, MIME type, and loading status of a <web_browser> widget
  2. getMediaText(path) — Returns the visible text content of the page (or a portion of it)


This repo is using Opire - what does it mean? 👇
💵 Everyone can add rewards for this issue commenting /reward 100 (replace 100 with the amount).
🕵️‍♂️ If someone starts working on this issue to earn the rewards, they can comment /try to let everyone know!
🙌 And when they open the PR, they can comment /claim #5682 either in the PR description or in a PR's comment.

🪙 Also, everyone can tip any user commenting /tip 20 @kurtlinden (replace 20 with the amount, and @kurtlinden with the user to tip).

📖 If you want to learn more, check out our documentation.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.