Chrome does not save context in file protocol when a document is saved
Reported by
bsabat...@gmail.com,
Dec 12 2016
|
||||
Issue descriptionI'm using Chome Version 54.0.2840.99 m I have a set of HTML pages on my local network that we access via file:// These pages have links to documents across our file server and I can write to them. I have Chrome setup so that MS Office products (WORD, EXCEL) launch when I click on a document of one of these. That is, I do not use the Chrome built-in office add-ons In IE, if I bring up one of these documents, modify it, and then save it, the document in the directory I launched it from in IE is updated; which is great. But on Chrome.. Chrome copies this document to the Chrome download directory and launches it from there.. So if I modify it, I do not modify the copy on the file server, but the one in my download directory, which I DON'T want. Anyway to change this behavior with Chrome? Thanks you, Bill
,
Dec 12 2016
Hello. I think I miss communicated. Yes, I know that Chrome does not do this. However, Internet Explorer and also Firefox do it. So it my humble opinion, Chrome SHOULD do it. Or at least, have an OPTION to turn the feature on. It is really a nice feature for file:// protocol. So can I make some sort of request to get it on a list for consideration at the next requirements review. Being a coder myself, I know it would be as easy thing.. taking the existing defined document path and adding it as the default working folder when the new thread is launched. Also, I don't suppose there are any workarounds for this? Right now, I have it setup so I launch the file:// HTML file from IE.. which nobody likes.. :) Thank you BIll
,
Dec 13 2016
,
Dec 15 2016
This is not a feature request we have ever received before. I am going to leave this bug open for a few weeks to see if there is broader interest.
,
May 11 2017
We haven't received any stars or additional requests for this feature. This is not something we are going to address at this time. |
||||
►
Sign in to add a comment |
||||
Comment 1 by nyerramilli@chromium.org
, Dec 12 2016