Closed
Bug 163842
Opened 23 years ago
Closed 23 years ago
Does not reload picture
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 121084
People
(Reporter: wwechsung, Assigned: asa)
Details
Thanks for making such a great browser! I mean it!
The 'bug': If you design a html site, naturally one takes a look at it with
every change made. Unfortunatly Mozilla does never ever reload a picture unless
it's name were changed. This is sort of a drag when you try out different logos
and stuff. Also ist's strange, I would understand it if the pages where chached
by name, in that case you could just put down the appropriat header but as
Dreamweaver works, the preview is always a temporary html file with a different
name each time around.
So there :-)
Comment 1•23 years ago
|
||
Well, do you check the option, in advanced/cache, "Compare the page in the cache
to the page on the network / every time I view the page" ?
It should help a little ;-)
If not, try it, and if bug is gone, tell us :-)
sounds like bug 121084 to me...
| Reporter | ||
Comment 3•23 years ago
|
||
i checked to see what option I had set, and you where right. BUT setting the
cache to 'Compare [..] everytime I view page' didn't yield any change. And
indeed, layout/color/text changes where always update correctly probably
because Dreamweaver always uses some weird temp file with unique/random name
for the 'Preview in Browser' option. So the first time you take a look, the
name of the file displayed in mozilla might be 'TMP1ma7k18kmp.htm' and the
second time it might look like this: 'TMP1n9bl18kny.htm' although its the very
same page.
It's just the pictures-
Comment 4•23 years ago
|
||
Well, it seems to be (as said in comment #2) a duplicate of 121084.
Mark it as duplicate of 121084.
Reopen this bug if I made a mistake.
*** This bug has been marked as a duplicate of 121084 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•