Feature requests for 1.6



  • @Pesala Wow... nope xD
    But it's useful only when user enable status bar 😉



  • @Pesala I do not understand your answer? (my message was in relation to the whole interface)



  • Add an option to disable "Typed history" in the address bar for privacy.

    Typed history will show when you press this button in the address bar:



  • Open Address in New Tab

    Add "Command + Enter" to this.

    (For Mac)



  • 1.6 Stable is now out. We should move on to the 1.7 Feature Requests thread.



  • @D0J0P said in Feature requests for 1.6:

    We should move on to the 1.7 Feature Requests thread.

    Gaelle has not created it yet, AFAIK, so posting in some other thread of that name won't achieve much. Perhaps we need to wait for the first 1.7 Snapshot to be released?



  • @Pesala I thought this was the 1.7 Feature Request thread: https://forum.vivaldi.net/topic/12915/feature-requests-for-1-7

    But then I realized that it's in the Windows category. If it could be moved to All Platforms, then we could just continue there.



  • @D0J0P said in Feature requests for 1.6:

    1.6 Stable is now out. We should move on to the 1.7 Feature Requests thread.

    Ah what's the point? These threads are huge and totally unmanageable, I doubt any sane developer ever goes through them.
    We already know what the feature requests for 1.7 are: All the features here that were not implemented yet.



  • @duarte.framos said in Feature requests for 1.6:

    I doubt any sane developer ever goes through them.

    Since gaelle, who started it, is the community manager, I am sure she will write a report for the developers if they don't have time to sort the thread by "upvotes" and read the first two or three pages.



  • @Pesala said in Feature requests for 1.6:

    Since gaelle, who started it, is the community manager, I am sure she will write a report for the developers if they don't have time to sort the thread by "upvotes" and read the first two or three pages.

    Ah yes good point, that would certainly help, but only solves part of the problem. The larger underlying problem remains though: Voting is totally skewed.
    The first posts will inevitably gather a whole lot more votes than the ones towards the end, not because more people want them or because they are higher on the priorities list, but simply because they are the most visible.



  • As each thread would be for a point update - 1.7; 1.8; 1.9 etc
    Why not limit each thread to a few pages and then "lock" for new posts whilst still allowing upvotes? That way each update would possibly have a manageable number of requests.

    We could also have another thread to collect "beyond next update" request/discussions.



  • @dougunlocked said in Feature requests for 1.6:

    @mrbenjoi it was my reply also to the OP @gaelle . One can wish different things, but with what is given now and what you suggesting the best bet would be creating several posts (main features) within one topic (e.g. Vivaldi 1.7). Then the users can reply to that main feature post they need to.

    • OP / Main feature post / wishes, wishes, wishes....
    • OP / Main feature post 2 / wishes, wishes, wishes....

    So, in @mrbenjoi's example

    • ...
    • ...
    • Feature Requests (All Platforms) // Vivaldi 1.7 or 1.x.x.x.x
      • Appearance // main feature post 1
        • Themes
        • User Interface
      • Tabbed Browsing // main feature post 2
        • Tabs // users' wishes for Tabbed Browsing
        • Tab-Groups // users' wishes for Tabbed Browsing
          • Tiling // wishes
      • Panel // main feature post 3
      • Bookmarks // main feature post 4
      • Session-Management // main feature post X
        • Saved Sessions // wishes for Session-Management
        • Startup //...
      • History // main feature post ...
      • Speed Dial // main feature post ...
      • Quick-Commands // main feature post ...

    Obviously, for organizational reasons and to not to be confusing, there can be only two levels for the tree-structure.

    I like to see the nested scheme for features request.
    Posting request should be allowed only if one read the whole thread (like an EULA to be clear), dupes should erased by mods or moved in the right request section (if wrong). Replies-to-replies should be hidden (but not erased as they can contain useful infos). When new feature request thread will be done, write to read everything before posting and an extensive explanation about the usage of upvote/downvote 🙂


  • Community Manager

    Thanks everyone for submitting your requests and voting for them. It's helping us greatly to see what you want. 🙂

    Also thank you for sharing your insights about feature request thread. We're always looking for ways to improve. 😉

    In the meantime if you want to vote for 1.7 here's the link to it: https://forum.vivaldi.net/topic/13217/feature-requests-for-1-7


  • Vivaldi Team

    @Stardust You can do this, albeit not in the address field. There are toggle buttons if you click on the % in the zoom slider.


  • Vivaldi Team

    @craight The whole address is visible in the status bar when you hover the link.


Log in to reply
 

Looks like your connection to Vivaldi Forum was lost, please wait while we try to reconnect.