Developer Diary
  • Developer Diary
  • 2019

    • June 2019
    • July 2019
    • August 2019
    • September 2019
    • October 2019
    • November 2019
    • December, 2019
  • 2020

    • January 2020
    • February 2020
    • March 2020
    • April 2020
    • May, 2020
    • June 2020
    • July 2020
    • August 2020
    • September 2020
    • October 2020
    • November 2020
    • December 2020
  • 2021

    • January 2021
    • February 2021
    • February 2021
    • April 2021
    • May 2021
    • June 2021
    • July 2021
    • August 2021
    • September 2021
    • October 2021
    • November 2021
    • December 2021
  • 2022

    • January 2022
    • February 2022
    • March 2022
    • April 2022
    • May 2022
    • June 2022
    • July 2022
    • August 2022
    • September 2022
    • October 2022
    • November 2022
    • December 2022
  • 2023

    • January 2023
    • February 2023
    • March 2023
    • April 2023
    • May 2023
    • June 2023
    • July 2023
    • August 2023
    • September 2023
    • October 2023
    • November 2023
    • December 2023
  • 2024

    • January 2024
    • February 2024
    • March 2024
    • April 2024
    • May 2024
    • June 2024
    • July 2024
    • August, 2024
    • September 2024
    • October 2024
    • November 2024
    • December 2024
  • 2025

    • January 2025
    • February 2025
    • March 2025
    • April 2025
    • May 2025
    • June 2025
    • July 2025
    • August 2025
    • September 2025
    • October 2025
    • November 2025
    • December 2025
  • 2026

    • January 2026
    • February 2026

July 30, 2019

Found on KRG that on a blog post they added a "sources" section and spelled out the links. In chrome, links won't break, causing them to run off their section and make weird margins.

overflow-wrap: break-word;

...will work, but I'm checking if it makes more sense to just not have the links like that.

SBX Analytics documentation, found a bad category for PartnerUniversity that should be Partner University that I'm just going to fix.

  • It was in Umbraco! Fixed.

A bit of time on Front-end guidelines

C's Jira 201 Training

TAP stuff

  • preloading
  • lazy loading
  • airtable connection for
    • forms
    • error tracking

Attempted Error tracking with Airtable. Unclear if it's working, going to be hard to debug with console logs.

  • Can't quite get this to work. It doesn't seem to be actually firing anything on error. Tabling for now. Tried...
window.onerror = function(error) {}
// and
window.addEventListener('error', function(error) {})

Just thinking, maybe one dev day we should just all share our coding extensions.

Airtable for simple form works well, will try a file upload next

  • looks like this isn't possible. You have to have a full URL first. Maybe I can use Filestack or Imgur according to this article from airtable
  • More likely, I'll need to use S3 or something like that.