All users were logged out of Bugzilla on October 13th, 2018

Support for WebDAV "source" property

RESOLVED EXPIRED

Status

--
enhancement
RESOLVED EXPIRED
15 years ago
9 years ago

People

(Reporter: ilya.konstantinov+future, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

15 years ago
Composer could support WebDAV-enabled content management systems much beter if
it would use WebDAV's "source" property, if available.

In WebDAV, a resource ("resource" as in URL-pointed resource) may have a
"source" property, which defines a URL by which the browser can retrieve the raw
unprocessed copy of the document, suitable for editing. Many CMS systems (e.g.
Zope) provide this property.

This page explains the reasoning behind this property further:
http://www.webdav.org/specs/rfc2518.htm#rfc.section.5.4

Use case:
1. User visits a page in the CMS and performs 'File | Edit Page'.
2. Composer performs a PROPFIND method on the current URL, listing "source" as
the property it wishes to retrieve.
   2.1. If PROPFIND method fails (web servers which don't support it will
respond with Method Not Allowed or Method Not Implemented), the editor loads the
current URL.
   2.2. If PROPFIND succeeds but the URL doesn't have a "source" property, the
editor loads the current URL.
   2.3. If PROPFIND succeeds and the "source" property exists for the current
URL, the editor will load the source's "dst" URL. If multiple "dst" URLs are
returned (should not normally happen but allowed by schema), the editor should
offer a choice.
Product: Browser → Seamonkey
Assignee: composer → nobody
QA Contact: composer

Comment 1

10 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED

Comment 2

9 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.