[MGNLUI-1600] URI decoding is not required anymore Created: 07/Jun/13  Updated: 10/Mar/21  Resolved: 10/Mar/21

Status: Closed
Project: Magnolia UI
Component/s: framework
Affects Version/s: 5.0
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Philip Mundt Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLUI-322 Location fragment should be escaped Closed
relation
is related to MGNLUI-1446 Performing a search in workbench with... Closed
is related to MGNLUI-1467 Space(s) in node name breaks the app Closed
is related to MGNLUI-1414 Upgrade to latest Vaadin Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

Vaadin 7.0.7 seems to have an impact on URI handling.
Further investigations needed.



 Comments   
Comment by Philip Mundt [ 10/Jun/13 ]

URI Encoding was needed because Vaadin double encoded the fragments and the changed fragment always caused a LocationChanged events, thus resulting in an endless loop. This was fixed in Vaadin 7.0.5 [1], therefore there shouldn't be anymore decoding required.

[1] http://dev.vaadin.com/ticket/10769

Comment by Philip Mundt [ 25/Jun/13 ]

We should remove decoding of fragments as Vaadin now handles URIs properly.
Re-Enable deactivated tests in URIEncodingUITest

Generated at Mon Feb 12 08:48:13 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.