-
Notifications
You must be signed in to change notification settings - Fork 974
Remove customTitle from siteDetail object #6585
Comments
I think removing custom title is wrong. |
I think if we did we would have to split out bookmarks from sites at the same time |
I think we should do it but I think we should split out bookmarks first or at the same time. |
@bbondy from the original discussion (sorry, should have posted this here too- @bradleyrichter had the same concern)
|
@bbondy the title updating itself is what causes several bugs unfortunately. For example, let's say the site ends up doing a redirect via JavaScript with a simple "we've moved" page. In this case, it'll rename the page "We've moved! Redirecting you now to so and so.com...." I tested with Safari and Chrome briefly and once a bookmark is saved, the title did not seem to be updated when visited again (if the page title was updated) |
If the title of a bookmark is updating currently on navigation then a bug was introduced, this used to work correctly. Still does as far as I can tell from testing just now. I'm ok and in favour of getting rid of
The |
Also you can still use the siteUtils for each of these but just store them differently in app storage. |
Great points @bbondy 😄 @NejcZdovc you can check the documention by @cezaraugusto for our existing "Site Detail" objects and behavior here: And @darkdh has modified that behavior further with #5587 (making each entry a hash instead, which is unique; PR is still open- pls feel free to review). Like @bbondy is saying, this is a great chance to remove bookmarks from the sites object 😄 Let's talk more on Slack if you have questions or want to talk about a design (we can then document any findings here) |
Blocked by #5587 |
I think splitting sites out is a good idea. We'll need to update Sync code to match the new schema. cc @diracdeltas |
i agree |
Resolves brave#6585 Auditors: @bbondy, @ayumi, @diracdeltas, @bsclifton Test Plan: - everything should work the same as before
@NejcZdovc is this issue still blocked on something? #6585 (comment) |
No it's not blocked anymore |
Resovles brave#9978 Resolves brave#6108 Resovles brave#6585 Resolves brave#6104 Resolves brave#3694 Auditors: @bbondy @ayumi @diracdeltas @bsclifton @darkdh Test Plan:
Resovles brave#9978 Resolves brave#6108 Resovles brave#6585 Resolves brave#6104 Resolves brave#3694 Auditors: Test Plan:
Resolves brave#1856 Resolves brave#2771 Resolves brave#3646 Resolves brave#3694 Resolves brave#4224 Resolves brave#4260 Resolves brave#4833 Resolves brave#4868 Resolves brave#4929 Resolves brave#5699 Resolves brave#6104 Resolves brave#6108 Resolves brave#6585 Resolves brave#8022 Resolves brave#9301 Resolves brave#9326 Resolves brave#9978 Resolves brave#10026 Auditors: Test Plan:
Resolves #1646 Resolves #1856 Resolves #2655 Resolves #2771 Resolves #3646 Resolves #3694 Resolves #4224 Resolves #4260 Resolves #4833 Resolves #4868 Resolves #4929 Resolves #5072 Resolves #5699 Resolves #5382 Resolves #6104 Resolves #6108 Resolves #6585 Resolves #8022 Resolves #9301 Resolves #9326 Resolves #9978 Resolves #10026 Auditors: Test Plan:
Resolves brave#1646 Resolves brave#1856 Resolves brave#2655 Resolves brave#2771 Resolves brave#3646 Resolves brave#3694 Resolves brave#4224 Resolves brave#4260 Resolves brave#4833 Resolves brave#4868 Resolves brave#4929 Resolves brave#5072 Resolves brave#5699 Resolves brave#5382 Resolves brave#6104 Resolves brave#6108 Resolves brave#6585 Resolves brave#8022 Resolves brave#9301 Resolves brave#9326 Resolves brave#9978 Resolves brave#10026 Auditors: Test Plan:
Test plan
#10136 (comment)
Discussion starts here #6108 (comment)
Removing this should resolve the following issues:
#6104
#6108
#3694
There are likely more which have this as the root cause (we can search for issues where titles change)
The text was updated successfully, but these errors were encountered: