-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Interface improvements (+ bring back Catch Text Links) #104
Comments
Hi @tarihci thanks a lot for the feedback and support ! Let me try and answer with some quick initial thoughts Catch Text LinksI can have a look at putting the text links option back. The hassle is detecting the link from a random click position, it didn’t even work that well I think. It’s a bit further from the core add-on functionality let’s say, which is why it got removed. You can still copy cleaned text links from selected text though. Please tell me if that’s enough for you of you’d rather see the catch text links option come back. Interface visual cuesI agree that the interface should be as easy to understand as possible. However there’s three different dimensions to display for each link, and I’m not entirely sure how to display those:
Currently 1 and 2 are filters and 3 is color-coded and has a utf icon. Buttons not actionableThat should be an easy fix. I’ll try some greyer greys. Tab-based behaviour
Only toggling the add-on on or off is per-tab, the cleaning behaviour is the same for all tabs. If it’s not, that’s a bug. |
I’ll see if we can do some sort of hierarchical display of what document the requests are related to. That’s not going to be an easy one, but I see how it could help getting an idea of what’s going on. |
Thanks for the quick response. :) I do use Catch Text Links frequently and rarely seen it not work. That's why I have been happy with and came asking for it, if possible. But, I understand that development is management of (time, mental energy, money, etc) resources, so I would understand if it is lower on your to-do list. I understand the complexity of visualizing several types and layers of things, but IMO the current layout is rather too flat and doesn't provide enough visual cues to understand types and layers. Hence, it is harder to chose type or layer to act on (ban, allow, or investigate). Currently we are all stuck at home, so I have some spare time. If you have time to work on it and don't mind an outsider's comments, I would be glad to give feedback on any visuals you would be willing to share. |
For the Catch Text Links, I can probably put it back pretty easily by fishing the code back out from the history, the new version of the code is now more modular. To sum up just so I’m clear, the exact feature you’re after is opening a cleaned text link when single-clicking it, without selecting it, right?
|
This is what the icon displays could look like. More work needed for the hierarchy. Any feedback (from you @tarihci or anyone else) is more than welcome. |
I apologize for not acting on my promise yesterday. I got buried in my own study-at-home project and forgot to check back with the thread. Just woke up, saw the emails from the thread, now here.
My past habit was as such: I used to click on a text link with left mouse button while holding ctrl, and would have the link opened in another tab. No highlighting or selecting the text was needed. It used to work just clicking anywhere on the link. And surprisingly well at capturing the link in full even if I clicked any part of it. Yes, currently it is quite cumbersome with extra steps. |
I read the visual changes explanation comment and looked at the images.
Further comments on the same image with my annotations:
I think this reports the addon's activity much clearer and in a much understandable visual way to the user. You can put multiple example images in the wiki with numbered sections for filter types and actions, and explain what is being done. So, people can visually understand and map what the addon is doing.
I think this is really good. The addon's activity is properly visualized and mapped, so that users can see each filter action for each filter type separately. An additional idea:
|
Yes the parent items will obviously get better indicators it’s work in progress right now. :) I think the “request type” filter as it is becomes slightly useless now: clicked items are always parents, requests always children, and header redirects are always childless items. One option is to use the classification you see in other logs and requests filters (maybe not icons just text): script / image / media / XHR / frame / etc. |
Yeah, you can decide on not showing these finer details of the process to the user. You can put them in the logs for technical scrutiny purposes, but choose not to show them to the average user. Also, in combination with #106, you may reconsider what CL is really for. My initial reason to search for and find CL was to eliminate unnecessary ad pages I had to go through while clicking on links. These blogs were putting file hosting links behind intermediary ad pages. With CL, I was able to jump the middle process and skip to the desired hosting pages. |
I think @tarihci is right, colorful icons are more visible and interactive. This can be a possiblity:
Disable and refresh/reload button can also be shifted to somewhere top. |
I think I’ll release a version with all the fixes so far pretty soon, and without the hierachical display yet. Hoewever, here's a step by step guide to test this (unfinished) display yourself:
|
I checked it out.
I will continue checking it further whenever you implement a new commit. |
Working on the text links. Can you add a screenshot of the buttons so I can see what’s unclear? For now they’re only greyed out if unavailable (e.g. no link selected). |
Also rename some options for improved readability.
I meant to say, the buttons on the lower right of the main display are not darker when clicked and do not have shade on them when I hover over them with my mouse. |
I tested after f99fe39 and could not get CL to recognize and click unclickable text links. |
Apparently my test swallowed a bug in computing the offset. Should be fixed now. |
So @tarihci and @Rtizer-9 you both brought up colour coding and I’m trying to look into it but it’s in fact not trivial.
Actually when testing some of the websites reported by @Rtizer-9 in #106 without an ad-blocker, the information was drowned out by ads/tracking/metrics requests that leaked the current pages’ URL. I think actually the best way to hide that would be to group requests per domain, so that a full ads/metrics/etc. domain can be collapsed. I still think there is value in modifying links from the previous page − e.g. when clicking a cleaned javascript link, it gets reported in the page in which it is clicked. You can only access that information from the next page. That probably means that we need a 2-level hierarchical display? |
I'm sorry for not making it more clear earlier itself; I was only talking about implementing color coding for the lower right buttons and not urls in the log and even that ONLY if you think it'll be a good idea. Also, IMO the urls in log looked more distinguishable with darker coding in earlier versions but frankly speaking the current implementation is completely fine. |
It works wonderfully now. |
I should have indicated that this was mostly a suggestion depending on a) doable with ease or not and b) if you also see that this could be an improvement to visualizing what the addon was doing to the user.
I agree with @Rtizer-9 on more colorful buttons on the lower right bottom in main display. But you may opt for a more subtle color palette as the developer. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Great Improvement 😊 |
First, if you don't mind sharing, I would appreciate a full view image of the main display window showing the whole icons set. My reason for this request is, color and design congruity within the whole set can only be judged by looking at the whole set. Secondly, although I like the colors and the green check mark, I agree with you in it becoming problematic in its placement within the icon box in comparison to the other elements, e.g. JS. Thirdly, that's why I suggest a frame, colored according to the meaning, around (some or all) icons. IMO, a frame around icons colored in green, orange, and red showing the decisions, would help the check mark problem. By employing a frame, you can decrease the size of the check mark. A smaller check mark would still make its point, but also render itself less problematic with other elements, such as JS. I took the liberty of making some amateurish adjustments: 1, 2, 3, 4, 5, and alltogether. I made the changes hastily in Paint, so there could be several mistakes. |
Here’s a recent screenshot of the popup with colour-coded buttons and hierarchical display of links in pages: I almost put the double arrow with an orange “1” and orange border for “allow once” but decided against it, as it does whitelist once the full link, including all removed parameters etc., and not just the redirect. Colour values are taken from the Mozilla style guide. |
Closing this issue now, as there is hierarchical display of cleaned links, and colouring on buttons. Let’s open new issues with more focused suggestions for further improvements. |
Hey man,
The issue I am writing for is the disappearance of "Catch Text Links" option. I was making use of it often and really liked it. Could you instate this option, if it won't be too much of a hassle?
As for my view on the new improvements, I like your effort and endeavor in updating and improving this addon. I really appreciate it. However, the interface can be improved for simplifying the general user base understanding and usage.
One example: I updated addon, browsed to my homepage (google search main page), clicked on top right google apps dots left of sign in button. It does not work, addon filters it. Yeah, fine, but I could not understand and find which of the filtered links is the one I am supposed to whitelist. Maybe a color code or indentation would help me understand?
I went back to old version, it only showed me a single link (https://ogs.google.com/widget/app/...) and I could whitelist that and move on. I know that new version does more and shows more, but I could not see which was a parent/child cleaning action and I could not differentiate which cleaned link to whitelist or allow. EDIT: I really didn't want to whitelist google completely and could not find out which filtered action is parent and which is child. I tested again and now I understand that it was a redirect filter, which is a higher degree of importance than tracking filter actions.
EDIT: When I open the same page in private mode, whitelisted action is gone and whitelist button was not actionable for re-whitelisting.
Tab based allow/ban might be a bit much. URL based is better. I can stop addon for certain URLs or whitelist for them. Same URL, different actions for different tabs is a bit much. Though, I saw this option yesterday and cannot find it now, maybe you thought the same too and removed it? Or maybe I am mistaken and this was not a case.
Although I like clean and simple interfaces, colored buttons for allow, whitelist, ban can be better for visual cues. For example, people use firewalls and understand red ban, green allow, white whitelist.
Related to that, the buttons at the bottom have very hardly distinguishable tones of gray. I could not understand why I could not click on whitelist or allow once for certain links/actions at first and realized that not all buttons are not actionable for all link types. But I could not see that from going over the button because the gray shading (for actionable/doable or not) was not enough.
Anyway, this is what comes to me naturally now. I will try to respond as time allows and if/when you comment/reply on my general thoughts. EDIT: I wrote this hastily without realizing that addon has a wiki now. I skimmed through quickly; it is well written and nice to have, but I still think that better visual cues are needed for the interface for more intuitive understanding and usage of the addon for general/less-code-savy users.
Thank you again for still caring for and working on this addon. The new version needs some work. We might get there in time and with some more work. Don't lose hope or be discouraged with peoples' quick decisions and harsh remarks. People just wish things to work from get go and it is often not the case, but they don't wish to be the one doing the work. :)
I look forward to hearing your response.
All the best,
The text was updated successfully, but these errors were encountered: