Closed
Bug 118549
Opened 23 years ago
Closed 11 years ago
Adobe Golive CyberStudio 5 Tracking (curDoc.layers, CSScriptLib, et al)
Categories
(Tech Evangelism Graveyard :: English US, defect, P1)
Tech Evangelism Graveyard
English US
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: doronr, Unassigned)
References
()
Details
(Keywords: meta, top500, Whiteboard: [author])
Adobe Golive 5 does not support us - you need to install a netscape 6 extension
(http://www.adobe.com/support/downloads/888a.htm for windows and
http://www.adobe.com/support/downloads/886e.htm for mac).
Adobe announced golive 6, which I assume will have support for us.
To see their nn6 version, I found
http://www.djdesign.com/test/test_nn6wipe.html. They also have a forum for
their NN6 addition at
http://www.adobeforums.com/cgi-bin/webx?50@65.jPIRaxqLmSg^1@.eec56dc
Updated•23 years ago
|
Keywords: meta
Priority: -- → P1
Summary: Adobe Golive 5 does not support us out of the box → Adobe Golive 5 Tracking does not support us out of the box
Comment 2•23 years ago
|
||
Confirmed GoLive 6 has support for NN6 out of the box.
Comment 4•22 years ago
|
||
Ok, this meta bug is on it's own and does not imply any work need to be done
with adobe. removing evang500 and block for adobe tracking
Adding some commonly found terms to the summary for easier tracking. I've
noticed several GoLive-created sites don't include the meta generator tag or
other direct references to GoLive.
Hardware: PC → All
Summary: Adobe Golive 5 Tracking does not support us out of the box → Adobe Golive CyberStudio 5 Tracking (curDoc.layers, CSScriptLib, et al)
Comment 7•21 years ago
|
||
tech evang june 2003 reorg
Assignee: bc → english-us
Status: ASSIGNED → NEW
Component: Authors → English US
QA Contact: mgalli → english-us
Whiteboard: [author]
Comment 8•11 years ago
|
||
GoLive was discontinued in 2008 in favour of Dreamweaver. Closing.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Updated•10 years ago
|
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•