Websites from history in "popular websites" section.

未关闭
#516 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
18/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
冷清
领域
mobile, search

调研方向

The payload names no files, tests or entry points, so a newcomer has to locate the address bar autocompletion and the popular websites list in the codebase first. The issue asks for a design decision rather than one change: whether history and bookmarks feed the popular websites list, and how that list replaces autocompletion. Done would mean a maintainer-agreed design, so confirm the approach in the thread before writing code.

由索引模型根据 Issue 内容生成。

描述

enhancement needs-triage

If we show also websites from history in popular websites section, and websites from bookmarks, we can choose tp disable autocompletion, because "popular websites" section will do everything autocompletion does and even more. But only main domains, not a distinct webpages.

Advantages of that.

  1. It will allow to go by click to alternative websites when autocompletion can have only one: for example if you type git you wi be suggested both with gilab and github, while autocompletion cant do more than one simultaniously. Which is already partially working, only with popular websites.
  2. If you want to search for github, autocompletion will complete it to github.com and you have to remove extra letters to not visit github but search for it.

So i suggest to make popular website section into sort of website database, where you will have initial popular websites and websites that user visited, so it always will be able to suggest corrwct websites, from history, bookmarks or just popular ones, and user will be able to disable autocompletion in adress bar entirelly. Even though autocompletion has its flaws that i described, disabling it currently is not viable untill you have an alternative that is good enough, which is point of this suggestion.

主要语言
Dart
星标
1k
派生
41
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

FaFre/WebLibre 的其他 Issue

查看 FaFre/WebLibre 的全部 Issue

相似的 Issue

更多 Dart Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。