Skip to content
Snippets Groups Projects

Resolve #3471093 "Mobile css"

Closes #3471093

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
1 1 .ct-starshot-case-study {
2 2 position: relative;
3 3 overflow: hidden;
4 padding-bottom: 174px;
5 margin-bottom: -174px;
4 padding-bottom: 74px;
5
6 @include ct-breakpoint(xl) {
7 padding-bottom: 174px;
  • Design shows the case study sitting over the component below. With these changes you've removed that feature:

    Screenshot_2024-09-06_at_9.30.44_AM

  • One possible solution to this might be that each of these organisms implement additional margin / padding when placed directly below the case study:

    .ct-starshot-case-study + .ct-starshot-hero,
    .ct-starshot-case-study + .starshot-listing-testimonial,
    .ct-starshot-case-study + .ct-starshot-case-study,
    .ct-starshot-case-study + .starshot-cta,
    .ct-starshot-case-study + .starshot-feature-cards,
    .ct-starshot-case-study + .ct-starshot-stats {
      margin-top: -74px;
      padding-top: 74px;
      z-index: -1;
    }

    Please note this 74px would need to accommodate for the breakpoint changes.

  • Fixed. Updated style as per above comment

  • Please register or sign in to reply
  • 5
    6 @include ct-breakpoint(xl) {
    7 padding-bottom: 174px;
    8 }
    9
    6 10
    7 11 &__background {
    8 padding-top: 141px;
    9 padding-bottom: 387px;
    10 12 background-color: #ccbaf4;
    13 padding-top: 60px;
    14 padding-bottom: 60px;
    15
    16 @include ct-breakpoint(xxl) {
    17 padding-top: 141px;
    18 // padding-bottom: 387px;
  • 114 @include ct-breakpoint(l) {
    115 border-radius: 25px;
    116 margin-top: 0;
    117 }
    118
    119 @include ct-breakpoint(xxl) {
    120 margin-left: -5px;
    121 }
    70 122 }
    71 123
    72 124 &__image-frame {
    73 125 position: absolute;
    74 top: -30px;
    75 left: -50px;
    126 width: calc(100% + 20px);
    127 height: calc(100% + 20px);
    • There's some cases around 1486px screen width and below where the image and frame are out of alignment and the image either sits outside the frame underneath, or too far to the left:

      Screenshot_2024-09-06_at_9.36.09_AMScreenshot_2024-09-06_at_9.38.10_AM

    • Please register or sign in to reply
  • 16 padding: 0 ct-spacing(3);
    17
    18 @include ct-breakpoint(xxl) {
    19 padding: 0 ct-spacing(2);
    20 }
    11 21 }
    12 22
    13 img {
    23 .stat-img {
    14 24 position: absolute;
    15 25 top: 0;
    16 26 right: 0;
    17 27 height: 100%;
    28 width: 25%;
    29 object-fit: cover;
    30 object-position: left;
  • 1 1 .ct-starshot-case-study {
    2 2 position: relative;
    3 3 overflow: hidden;
    4 padding-bottom: 174px;
    5 margin-bottom: -174px;
    4 padding-bottom: 74px;
    5
    6 @include ct-breakpoint(xl) {
    7 padding-bottom: 174px;
    8 }
    9
    6 10
  • Thanks @Bhut.Avani - please see the comments in the MR.

  • Alan Cole requested changes

    requested changes

  • Alan Cole requested changes

    requested changes

  • @alan.cole There's a merge conflict when merging in main to here. Can you resolve?

  • @Bhut.Avani talked with Alan and it's best if you merge 1.0.x into your MR branch and resolve the conflicts along with the things above. Thanks.

  • Alan Cole changed target branch from feature/civictheme-font-integration to 1.0.x

    changed target branch from feature/civictheme-font-integration to 1.0.x

  • Alan Cole added 27 commits

    added 27 commits

    Compare with previous version

  • Hi @kepol, @Bhut.Avani - I've updated the fork 3471093-mobile-css branch to resolve the conflicts. Please git pull --rebase before continuing work, as I have force-pushed a rebase.

    Edited by Alan Cole
  • Kristen Pol bypassed reviews on this merge request

    bypassed reviews on this merge request

  • Talked with Alan and the follow up cleanup should happen in a new MR as we need to get this code merged to unblock other things.

  • merged

  • Please find updated code in this MR !52 (closed)

  • Please register or sign in to reply
    Loading