2

Feature Overview

This feature involves enhancing the default WebKit's developer tools by adding an option to render the response. It is specifically designed for web developers using Orion, providing them with improved capabilities to handle various response types effectively.

Purpose and Target Audience

The primary purpose of this feature is to assist web developers who rely on Orion for their development tasks. By enabling the rendering of responses directly within the developer tools, developers can more easily inspect and debug their web applications. This is particularly useful in scenarios where there has been an error in the API backend, and instead of returning JSON, the response is in HTML format. The feature caters to a niche segment of the Orion user community—those who require sophisticated debugging and development tools.

Impact on Workflows and User Experience

While this feature simplifies certain tasks for web developers, it is designed to have minimal impact on the broader user base that uses Orion primarily for browsing. For developers, it provides a more efficient way to diagnose issues by allowing them to view unexpected response formats directly within the developer tools.

Usage Scenarios for the Proposed Feature

The proposed "Response (HTML Viewer)" feature in Orion's developer tools will allow developers to directly view and analyse HTML content in API responses. This is particularly useful when an API returns HTML instead of the expected JSON.

Comparison with Other Browsers

  • Firefox: Offers a robust preview feature that allows developers to toggle between raw and rendered views, providing flexibility in how content is analysed.

  • Chrome: Provides a simpler HTML preview that renders the content without executing external CSS or JavaScript, focusing on the structure rather than the full rendered page.

Integration with Existing Features

Orion, which is based on Safari, currently offers two response viewing options: "Response" and "Response (DOM Tree)." The addition of "Response (HTML Viewer)" would serve as a third option, specifically designed to render HTML content directly. This feature could be set as the default view for HTML responses (by content, not by headers), ensuring developers have immediate access to the information without needing to adjust settings manually.

  • Vlad replied to this.

    Giancarlo This sounds like a suggestion to be posted on webkit.org (who maintain the developer tools).

      Vlad Thanks for reviewing this suggestion! I don't have experience in raising these with the WebKit team, do I simply raise it in their Bugzilla as a feature request?

      • Vlad replied to this.
        No one is typing