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

Implement Endpoint: /core/browse-happy #45

Closed
chuckadams opened this issue Oct 22, 2024 · 3 comments · Fixed by #173
Closed

Implement Endpoint: /core/browse-happy #45

chuckadams opened this issue Oct 22, 2024 · 3 comments · Fixed by #173
Labels
backlog Not scheduled on any project or milestone enhancement New feature or request
Milestone

Comments

@chuckadams
Copy link
Contributor

Whatever the gosh-darn heck this endpoint actually does, let's do it too

@chuckadams chuckadams added this to the Phase 1 milestone Oct 22, 2024
@yosefeliezrie yosefeliezrie added the enhancement New feature or request label Oct 27, 2024
@yosefeliezrie
Copy link

The Browse Happy API—which detects a browser via user-agent string and determines and returns some basic information about certain browsers, including if it needs an update or is insecure—is developed as a separate project. This API is used by the WordPress.org software for the admin dashboard widget that alerts a user if they are using an outdated or insecure browser.

The code for that project can be found at https://meta.svn.wordpress.org/sites/trunk/api.wordpress.org/public_html/core/browse-happy/ and here https://github.com/WordPress/browsehappy.

WordPress.org core tract has a "Browse Happy" component at https://meta.trac.wordpress.org/

@chuckadams
Copy link
Contributor Author

Actually I'm not sure if the separate browsehappy project is used, the endpoint appears to be pretty well contained here: https://github.com/WordPress/wordpress.org/blob/e5a07055d2ddf239cc20f752bc182bed70a15d5f/api.wordpress.org/public_html/core/browse-happy/1.0/index.php

@chuckadams chuckadams modified the milestones: MVP API, Full API Nov 2, 2024
@chuckadams
Copy link
Contributor Author

The whole concept of browse-happy is obsolete with modern evergreen browsers. Moving to backlog.

@chuckadams chuckadams added the backlog Not scheduled on any project or milestone label Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Not scheduled on any project or milestone enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants