Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: webcontents #5

Open
1 task done
trulysinclair opened this issue Oct 17, 2024 · 0 comments
Open
1 task done

feat: webcontents #5

trulysinclair opened this issue Oct 17, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@trulysinclair
Copy link
Owner

Preflight Checklist

  • I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Problem Description

BrowserWindow, BrowserView, and WebContentsView all have a webContents property which can be handled by a dedicated WebContents class from which the wrapping classes, Window and View, can extend from.

Proposed Solution

The WebContents class should contain common logic for representing favicons, title, themeColor, url, isMediaPlaying and more. This class will also handle listening to a variety of events to keep a consistent state such as whether the page is loading, crashed, unresponsive, ready, or destroyed.

Alternatives Considered

N/A

Additional Information

N/A

@trulysinclair trulysinclair added the enhancement New feature or request label Oct 17, 2024
@trulysinclair trulysinclair self-assigned this Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant