Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Contribute to GitLab
  • Sign in / Register
V
V8
  • Project
    • Project
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Linshizhi
  • V8
  • Repository

Switch branch/tag
  • v8
  • test
  • inspector
  • debugger
  • eval-without-codegen.js
Find file
BlameHistoryPermalink
  • Peter Marshall's avatar
    inspector: Add flag to Runtime.evaluate() for unsafe eval · f510c66b
    Peter Marshall authored Jun 19, 2020
    evaluate() bypassed CSP for unsafe-eval by default. This is a useful
    option for debugging clients, but is not always what we want.
    
    e.g. in the devtools console we want to match the page's CSP settings
    to make debugging CSP issues on the page easier.
    
    Add a toggle that keeps the current behavior by default.
    
    Bug: chromium:1084558
    Change-Id: Ia01142d5be00f8ef5f65e5eeba17549efc6f9120
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2250245
    Commit-Queue: Peter Marshall <petermarshall@chromium.org>
    Reviewed-by: 's avatarSimon Zünd <szuend@chromium.org>
    Reviewed-by: 's avatarYang Guo <yangguo@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#68432}
    f510c66b
eval-without-codegen.js 2.72 KB
EditWeb IDE

Replace eval-without-codegen.js

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.