| Summary: | [client] The editor does not work for some URIs | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Szymon Brandys <Szymon.Brandys> |
| Component: | Client | Assignee: | Project Inbox <e4.orion-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | mamacdon, Silenio_Quarti, susan, tomasz.zarna |
| Version: | 0.2 | ||
| Target Milestone: | 0.2 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 334213 | ||
|
Description
Szymon Brandys
In coding.html we use the hash to store the URL of the resource being edited, and also to provide "line" and "char" parameters in a query-style format, Eg. coding.html#/path/to/file.txt?line=25&char=6 This is ambiguous when the resource URL includes "?&". For example we can't distinguish between > coding.html#file.txt?parts=body and > coding.html#file.txt?line=25 This is a design issue that we need to solve. To stop blocking Szymon, I've made coding.html more conservative when it parses the hash. It now only assumes that "char" and "line" are parameters for the editor, and leaves stuff like ?parts=body alone. I opened Bug 340458 for discussion of our hash-usage approach. |