Closed
Bug 87464
Opened 24 years ago
Closed 24 years ago
Unable to edit opened files in Editor
Categories
(Core :: DOM: Editor, defect)
Tracking
()
People
(Reporter: jubal+mozillabugs, Assigned: rubydoo123)
Details
This is a strange one, and pretty bad. I hope I'm not doing something critically
stupid, as in "Oh, you're missing a step or three," but anyway, here's what happens:
1. In Browser, I select a file:// or http:// location, for example
File -> Open File...
File -> Open Web Location...
2. The page shows up in Mozilla Browser
3. I go to File -> Edit Page
4. Composer opens, but the page I intend to edit is read-only. I can't edit
anything.
Now, I close and restart Mozilla a few times, then open Composer without using
Browser to select a file/URL for reading. Then I select a file or URL (tried
both) from the Composer menu. I still can't edit any page that opens.
I couldn't find anything in bugzilla matching this. It's bad. It's driving me
crazy. All I want to do is open a preexisting HTML file on my local disk and
edit it!@#
|
Reporter | |
Comment 1•24 years ago
|
||
Welp, I figured it out. Apparently having a:
<LINK REL="stylesheet" TYPE="text/css" HREF="/file.css>
line in the <HEAD> container will prevent Editor from opening the file for
actual editing. Just browsing only.
I don't know what to say at this point, as I can sort of see the mess that
editing a CSS-dependent file would cause. However, I really doubt everyone who
attempts to edit a CSS-dependent page, and tears hair out at this seeming bug or
whatever it is to be called that prevents the page from being edited -- I
sincerely doubt most of these people will figure out Mozilla may be doing it on
purpose.
Which leads me to this Request for Something {Enhancement,DOcumentation}.
Please put a banner, a dialog, a SOMETHING to tell the user that Editor cannot
edit the files because it contains CSS.
Of course, the ideal fix would be CSS support, but god damn, I sure wish I
hadn't wasted time because nobody bothered to implement a warning string or
something to notify me that my attempts are as futile as polishing a ****.
(I erased the <LINK REL> statement and continued on my way.)
Summary: Unable to edit opened files in Editor → Unable to edit opened files in Editor
Please always include Mozilla build ID in bug-reports
.
With a current CVS build, Linux, I can edit pages on local dish with LINK REL's
to stylesheets on disk just fine.
Are you sure your link to it is correct? Does file.css really live in the root
directory? And if it does : who owns the file? The user you run mozilla as or
someone else?
Ahh forgot: Please also inform about the file attributes on file.css
|
|
Reporter | |
Comment 4•24 years ago
|
||
Linux build 20010622.
I think I've narrowed the problem. Mozilla cannot (will not?) open HTML files
for editing if the URI prefix is file:// AND the target file has a LINK REL
statement pointing to a CSS file whose path is absolute, according to the httpd
document root for the website.
For example, if the LINK REL statement is:
<LINK REL="stylesheet" TYPE="text/css" HREF="/file.css>
and I open the file with file:///usr/home/jubal/web/index.html, Mozilla will
fail to edit the file, because, presumably, /file.css does not exist on the
local filesystem.
I hope that makes sense.
What I'd suggest for this issue is, if Editor encounters a file:// open request
and the LINK REL's HREF value is a path not found on the filesystem, present a
warning to the user that says:
"File dependency /file.css not found on local filesystem. Continue editing? [Y/N]"
Agree? What do you think.
Possibly dup of bug 72583 (patch pending)
Editing from a local webserver would be a workaround i guess.
|
|
Reporter | |
Comment 6•24 years ago
|
||
I am using a local webserver.
I read bug 72583, and I can't tell if the suggested patch(es) will address the
problem of Mozilla being unable to edit a file.
I want Mozilla to open a file for editing, regardless of problems with CSS links
being absolute or relative. Then I can edit the source and save to a different
location if I wish. Right now I can't.
Please don't mark this as a dupe unless you're 100% sure....
|
Assignee | |
Comment 7•24 years ago
|
||
*** This bug has been marked as a duplicate of 84191 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•