News for hackers. Stuff that matters.
Re:New in Chrome 66 by kaycebasques on Wednesday April 18, 2018 @11:38AM (#16868218)
That's me! Questions / feedback welcome
Re:New in Chrome 66 by LethargicStud on Wednesday April 18, 2018 @12:18PM (#16868574)
Thanks for all the great work on dev-tools. I recently started developing a chrome extension and found that not all of the great standard functionality was present. Here were some of the main pain points:

- debugger; statements do not work for me

- When right clicking the extension and clicking Inspect Popup, the first few network requests are not reported in the network tab (seems that it starts recording after the extension opens)

- It took a very long time for me to figure out that cookies were not being set due to this permission: (https://developer.chrome.com/extensions/declare_permissions)

- Hot-reloading extension code would be extremely nice

Even just extra documentation on dev-tools with extensions or tips/tricks for debugging extensions would be excellent - I haven't been able to find much in the way of docs. Keep doing the excellent work you're doing, just thought I'd give some suggestions :)

Re:New in Chrome 66 by kaycebasques on Wednesday April 18, 2018 @12:36PM (#16868743)
Learning more about Extensions is one of my nagging TODOs. I'll see if our Extensions writer is up for the task, otherwise I'll take a crack at it this quarter. Thanks for the specific feedback.
Re:New in Chrome 66 by aleem on Thursday April 19, 2018 @04:55AM (#16874343)
I have a few things that have been bothering me forever.

Push Notifications Prompts break the back button. Many times I hit a search result on Google, find the page is irrelevant but I can't go back. That's because the page has prompted a push notification. I can't scroll either. It blocks the whole UI. That's very disruptive.

Second, while Postman is wonderful, Chrome's network tab is the super convenient. A very small change to allow replay requests to work via a keyboard shortcut would make a significant impact on the dev cycle. The use-case is to modify the server code then replay the request, rinse, repeat. The alternative is to copy-as-curl or proxy via postman, etc.

Re:New in Chrome 66 by kaycebasques on Thursday April 19, 2018 @10:09AM (#16875971)
Yeah, replaying requests is a feature request we get often. I’ll add your comment to the tracker.

I haven’t heard of that problem with push notifications. That’s not our area but I’ll forward it to the Chrome team.

Re:New in Chrome 66 by spiralx on Friday April 20, 2018 @09:28AM (#16884558)
Any chance of being able to save the network filter? It takes ages to re-enter a set of filters for request type, source, name etc. on every page refresh, to the point where I've got a bookmarklet so I can at least just copy and paste it in every time.
Re:New in Chrome 66 by csours on Wednesday April 18, 2018 @03:24PM (#16870225)
Is there an idomatic way to associate local and web-served files for apps under development? It sure looks like it, but I can't figure it out.
Re:New in Chrome 66 by kaycebasques on Wednesday April 18, 2018 @04:35PM (#16870928)
Re:New in Chrome 66 by csours on Wednesday April 18, 2018 @07:41PM (#16872229)
Thanks!
Re:New in Chrome 66 by CapitalistCartr on Wednesday April 18, 2018 @03:59PM (#16870610)
Needs access to: Device & app history, Location, Identity, Photos/media/files, Camera, Microphone, Other.

So, everything.

Re:New in Chrome 66 by kaycebasques on Wednesday April 18, 2018 @04:34PM (#16870917)
Are you talking about accessing location, files, camera, and microphone from web browsers? Those are all already possible. For identity, there's various libs and APIs for authenticating with major identity providers. Not sure what you mean by device and app history.
Re:New in Chrome 66 by CapitalistCartr on Wednesday April 18, 2018 @06:34PM (#16871857)
That's the list this browser requires authorization before installation is allowed. Its not about what's possible; its what intrusiveness Chrome demands. Maybe there's a good reason for each one, and the browser will act in good faith.
Re:New in Chrome 66 by kaycebasques on Wednesday April 18, 2018 @07:14PM (#16872088)
In order for a website to access camera, microphone, etc., the browser itself needs permission to access those things. The browser prompts you to grant each individual permission to specific sites that request them.

I personally agree though that if you don't want any site to ever have access to camera (for example) there should be a way to install the browser without that permission enabled. Maybe there is? I'm not completely familiar with the iOS / Android / other mobile OS install workflows these days.