New issue
Advanced search Search tips

Issue 765294 link

Starred by 3 users

Issue metadata

Status: Untriaged
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Feature



Sign in to add a comment

Request for improvements to view source page

Reported by d...@dan-atkinson.com, Sep 14 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.79 Safari/537.36

Steps to reproduce the problem:
I have previously detailed a list of several requested enhancements to the ViewSource implementation that I believe would be useful to developers such as myself.

What is the expected behavior?
Either the ability for users to extend the ViewSource functionality in the extensions API, or for the improvements to be baked directly into the browser.

What went wrong?
These include:
* The ability to use regex in the find box.
* The ability to use case sensitivity in the find box.
* The ability to go to a specific line in the source (eg Ctrl+G).

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 61.0.3163.79  Channel: stable
OS Version: 10.0
Flash Version: 

I don't believe that this is the correct place to put this, but I don't know where it should go. If I'm correct in assuming this, please let me know where I should put the requests. Thanks.
 
Labels: Needs-Triage-M61
Labels: -Type-Bug -Needs-Triage-M61 Type-Feature
Status: Untriaged (was: Unconfirmed)
Components: UI>Browser>FindInPage
The first two of these are requests for the Find box. Issue 687552 is the request for case-sensitivity in Find. 
Yes please add support for regex in the find box. Please see request from others in the older issues (590739, 290816, 352078)

Sign in to add a comment