There is a difference in the way that coreapps display some views as of the latest SNAPSHOT. An example is the patient page that displays as below in a full-sized browser window. It is possible that this could be breaking my end by something missing.
@ssmusoke, @ayesh, could I be missing a point on the work that was completed and merged on the related project ticket RA-1592. This works probably as intended on mobile devices but seems backwards incompatible on desktop browsers. I am using Chrome(Version 76.0.3809.132) and firefox(quantum 68.0.1).
I’ve reproduced this on a local instance. You may reproduce this by building the coreapps module cloned from github and installed on a fresh Ref App instance. We could probably jump on a call so I demonstrate this here https://uberconference.com/openmrs
@ayesh there are other UI issues that are visible. A fairly major one is that it is not possible anymore to start a visit since everything, including the confirmation popup, become part of the greylined background:
@ayesh there are clearly a couple of changes that are either breaking the UI or that are subject to debate. In the latter category, see how the buttons are of different sizes on the apps screen:
@ruhanga You are probably not missing anything, migrating to bootstrap is an involved process, hence the drive to merge and get it tested out quickly to identify the different elements we may have missed
I actually noticed that.And the problem is fixed as well.
As I opened a new talk thread to ask about this issue I mentioned below in that thread
When it comes to the reference application module after it’s build it’s creating a folder call sass-external.In here it refers to uicommons module sass files. Like below image !
My question is it’s always referring to the ui commons without latest changes in github means to a former build or a released version.How can we change it to point to the new changes in the github.
It’s because when it comes to :- “https://qa-refapp.openmrs.org” it’s referring to latest changes in github so things are not working well without latest commons module changes.
@ssmusoke so you’re expecting some real-time QA from the community? I guess that’s the only way to really get things moving, but it’s a little… brutal maybe?
Is there a place where we can gather this feedback?
Unfortunately we had to use that approach, so that @ayesh can complete his GSoc project that has been over 20 months in the making.
Just keep sharing it here, since he is currently working across 6-8 different modules, which is the tough part… I feel for him, but he has not broken down yet
.Shall I send a PR with the fix for that.
