Browser features such as camera, location, clipboard, and sharing cross a trust boundary. Availability, permission state, user activation, and device conditions vary. A useful interface explains the action before asking, offers a manual path when access fails, and releases resources when work ends. This track uses field-case intake: an operator may attach a photo, add an approximate place, copy an identifier, or share a review link. Each step must still work when a prompt is dismissed or an API is absent.
Topics in this track
- Permission Request Timing and Manual Fallback — Ask for browser access at the point of use and preserve a useful manual path after denial.
- Camera and Microphone Capture and Track Cleanup — Start media capture after intent, stop every track, and separate preview from trusted upload.
- Geolocation Accuracy, Cancellation, and Retention — Use location with a stated purpose, bounded waiting, accuracy context, and minimal retention.
- Clipboard and Share Activation Fallbacks — Handle user activation, capability gaps, and rejected share actions without losing the content.
Prerequisite paths
Offline and Device Capabilities; Browser Security and Data Stewardship.
Neighbor track
Overlays, Scroll, and Mobile Viewport.
Practice path
Build Project: field intake with capability fallbacks and check decisions in Web Development: browser capability and viewport decisions quiz.
Further connections
Web Push and Notification Delivery; Notification Opt-In and Channel Preference.
Further connections
Progressive Browser Compatibility; Feature Probes and Functional Fallbacks.
Further connections
Browser Extension Trust and Lifecycle; Extension Host Permissions and User Invocation.