Dark mode styles makes our page unreadable

[jedie]

The "dark mode styles" was added with: 7fc0662 for: #1318

Our page doesn't support dark mode yet. So these styles makes the diff unreadable.

A work-a-round, that we currently use is to add these styles in our css file:

@media (prefers-color-scheme: dark) {
  /*
  Work-a-round for https://github.com/django-import-export/django-import-export/pull/1323
  */
  html table.import-preview tr.skip {
    background-color: #d2d2d2;
  }

  html table.import-preview tr.new {
    background-color: #bdd8b2;
  }

  html table.import-preview tr.delete {
    background-color: #f9bebf;
  }

  html table.import-preview tr.update {
    background-color: #fdfdcf;
  }

  html .validation-error-container {
    background-color: #ffc1c1;
  }

  /*
  these declarations are necessary to forcibly override the
  formatting applied by the diff-match-patch python library
   */
  html table.import-preview td ins {
    background-color: #bdd8b2 !important;
  }

  html table.import-preview td del {
    background-color: #f9bebf !important;
  }
}

That will "reset" the dark colors to "normal" ones...

[matthewhegarty]

Thanks for raising this. Can you give me some more information as to what the issue is... How do you reproduce it? Can you add some screenshots? What browser is this etc.

[jedie]

Sorry, i can't create a screenshot... (They will display internal information)

We still use Django 2.2... Don't know if the admin has "dark"-Styles ?!? I don't think so. So it can't work with 2.2?!?

EDIT: dark them was added in Django 3.2, see: https://docs.djangoproject.com/en/3.2/releases/3.2/#django-contrib-admin

[matthewhegarty]

I tested using the example app on django 2.2. It renders ok for imports, but I notice that if you switch to dark mode in the browser then there is an issue where the text is not legible (below). Is this what you are seeing?. Can you confirm if you are browsing in "dark mode"? If, so, what happens if you switch to 'light mode'?

[jedie]

That is exactly how this "bug" looks like here:

[matthewhegarty]

We have reverted this change and the updated css is now released in 2.6.1