Code Monkey home page Code Monkey logo

brave's People

Contributors

evandandrea avatar flexiondotorg avatar popey avatar posix4e avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

Forkers

ads20000 brave popey

brave's Issues

No Microsoft (Core) Fonts support

On Solus (distro) with "mscorefonts" successfully installed and able to be used in Firefox, sites like Google Docs do not show "Arial" or "Times New Roman," indicating the Brave snap is not able to find them.

I confirmed this by downloading the .bz2 version of 0.18.29 (same as current Snap) and noticed the text within the UI is much crisper than the Snap version. As expected, Google Docs successfully defaulted to Arial using the .bz2 version while no such option appears in the Snap.

Brave not building

Perhaps this is part of the handover process but @flexiondotorg put v0.18.23dev in the repository but we haven't released it because it's not building on the build service (I note that the publisher field in the store is empty). Any way of getting this release out ourselves soon or do we need to wait for the handover process to be complete?

Needs `contact` field

Since we haven't yet handed over the snap... ( #1 )

Brave needs a contact field in the store. Probably should be https://github.com/snapcrafters/brave/issues.

Chinese and Japanese fonts don't work

Japanese and Chinese fonts don't display. Jamesh from the snapcraft.io forums made a suggestion to add the line "-desktop" to the plugs section. Supposedly, this should allow Brave to use system fonts, which should fix the problem. (Chinese and Japanese fonts work in Firefox and Chrome on my system.)

https://forum.snapcraft.io/t/issue-with-fonts-in-brave/2948/5

I'd submit a patch myself, but I have no idea how to test snaps.

I'm on Solus MATE edition.

".desktop" file needs to be named correctly

On Solus (a Linux distro), I have installed Brave using snap.

I couldn't get Brave to pin to the panel in Budgie (the Desktop Environment). After inquiring about it, I found out the name of the generated ".desktop" file (for me it is located in /var/lib/snapd/desktop/applications) needs to match with the window's WM_Class(string).

For Brave, this string is "brave," while the generated file is named "brave_brave.desktop," which can be easily renamed but I believe will be replaced upon an update to Brave.

I assume other Desktop Environments adhere to this standard also, as Budgie is derived from GNOME 3.

Won't start

Installed from "Ubuntu Software" on Ubuntu 17.10 but won't start.

tail /var/log/syslog -f

Feb 9 11:04:41 Upstairs-Latitude-E6230 gnome-software[1930]: running search with refine-flags=require-icon with timeout=60 with max-results=20 with search=brave on plugin=snap on apps system/snap/Snap Store/desktop/brave/* took 1732ms

unable to set timezone

I'm not exactly sure why, but everything in my brave snap is 2 hours behind. Which I assume is related to the timezone.

Removing the snap remove the current data directory

After an autoupgrade to the Chromium forked version, I removed the old Brave snap. When I notice my bookmarks had not been automatically imported, I looked at ~/snap/brave but the data folder which current had been linked to was removed when I removed the snap. I still had data from redundant folders created from previous upgrades: 18 32 33.

Isn't the standard practice to leave the data directory intact when removing snaps and apt packages?

Brave snap crashes when handling web links as default web browser

Hey folks! I tried out the Brave snap this afternoon because I wanted to see if this bug would be present—I've been having the same issue packaging Mailspring as a snap.

If you install the Brave snap and then make it the default web browser through Settings > Details > Default Applications (on Ubuntu 16), when you click a link to a web page in an application, the running copy of Brave is killed and a new copy of Brave launches to handle the link. I believe this is caused by a snapd issue with Electron's app.makeSingleInstance API, but I haven't gotten to the bottom of it yet: https://forum.snapcraft.io/t/electron-snap-killed-when-using-app-makesingleinstance-api/2667/17. Just wanted to let you know!

Default Download Location Within ~/snap Subdirectory.

Brave by default seems to push downloads to a directory within the user's ~/snap folder (see screenshot, please) (Also note that I'm not entirely proficient in Snap tech and don't know the technicalities of this, so I'm not sure of additional detail I may otherwise be able to provide)
image

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.