Package: chromium Followup-For: Bug #982062 X-Debbugs-Cc: pitsior...@gmail.com
So, in your opinion, a browser is useful only for rendering pages? Nowadays, web technologies have evolved and web pages are not static html. Sites are complex and the ability for someone to sync passwords/bookmarks/history in his browser helps him have some continuity for his work, even on different devices. For some, sync is not just another browser feature but a critical feature the browser MUST have. Leaving sync aside, these are the features that are expected to break Geolocation Click to Call Chrome spelling API Contacts API Chrome translate element Speaking for myself and only for myself, I am not affected by any of these. But I am not the average user. Other major distros have already announced or are discussing what they will do. Fedora has even removed their api keys already! Slackware is asking users if they are willing to use a muzzled browser. Why? Because building chromium takes a lot of time and that cut in usability may not worth it. Finally, if you consider this a minor issue, make an announcement beforehand so the users know what to expect by then and remove /etc/chromium.d/apikeys from the package on a future update, because it will be useless. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-3-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages chromium depends on: pn chromium-common <none> ii libasound2 1.2.4-1.1 ii libatk-bridge2.0-0 2.38.0-1 ii libatk1.0-0 2.36.0-2 ii libatomic1 10.2.1-6 ii libatspi2.0-0 2.38.0-2 ii libavcodec58 10:4.3.1-dmo10 ii libavformat58 10:4.3.1-dmo10 ii libavutil56 10:4.3.1-dmo10 ii libc6 2.31-9 ii libcairo2 1.16.0-5 ii libcups2 2.3.3op2-2 ii libdbus-1-3 1.12.20-1 ii libdrm2 2.4.104-1 ii libevent-2.1-7 2.1.12-stable-1 ii libexpat1 2.2.10-1 ii libflac8 1.3.3-2 ii libfontconfig1 2.13.1-4.2 ii libfreetype6 2.10.4+dfsg-1 ii libgbm1 20.3.4-1 ii libgcc-s1 10.2.1-6 ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1 ii libglib2.0-0 2.66.6-1 ii libgtk-3-0 3.24.24-1 ii libharfbuzz0b 2.7.4-1 ii libicu67 67.1-6 ii libjpeg62-turbo 1:2.0.5-2 pn libjsoncpp24 <none> ii liblcms2-2 2.12~rc1-2 pn libminizip1 <none> ii libnspr4 2:4.29-1 ii libnss3 2:3.60-1 ii libopenjp2-7 2.4.0-1 ii libopus0 1.3.1-0.1 ii libpango-1.0-0 1.46.2-3 ii libpng16-16 1.6.37-3 ii libpulse0 14.1-1 pn libre2-9 <none> ii libsnappy1v5 1.1.8-1 ii libstdc++6 10.2.1-6 ii libvpx6 1.9.0-dmo1 ii libwebp6 0.6.1-2+b1 ii libwebpdemux2 0.6.1-2+b1 ii libwebpmux3 0.6.1-2+b1 ii libx11-6 2:1.7.0-2 ii libxcb1 1.14-3 ii libxcomposite1 1:0.4.5-1 ii libxdamage1 1:1.1.5-2 ii libxext6 2:1.3.3-1.1 ii libxfixes3 1:5.0.3-2 ii libxml2 2.9.10+dfsg-6.3+b1 ii libxrandr2 2:1.5.1-1 ii libxslt1.1 1.1.34-4 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages chromium recommends: pn chromium-sandbox <none> Versions of packages chromium suggests: pn chromium-driver <none> pn chromium-l10n <none> pn chromium-shell <none>
