Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Add option to preserve pre-existing HTML sizes attributes on images

Abierto
  • ¿Algo no está bien?
#1,115 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
52/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
php
Área
web-dev

Línea de trabajo

Empieza por localizar el flujo de opciones de Optimole y el analizador de etiquetas HTML responsable de reemplazar los atributos sizes. Determina cómo deberían representarse la configuración o el atributo de datos compatible y, después, añade cobertura de pruebas unitarias para conservar los atributos sizes preexistentes. Se considera terminado cuando una configuración activa deja esos atributos intactos.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

customer report feature-request-triage

Impact: 75 · Confidence: 95 · Complexity: 35

Description

Problem

When Optimole processes frontend images, its Page Profiler replaces existing HTML sizes attributes with automatically measured slot dimensions. Site developers who have crafted accurate sizes attributes (e.g. for hero images or complex responsive layouts) find their attributes overwritten. Currently, the only way to prevent Optimole from replacing a sizes attribute is using CSS function workarounds like calc(100vw).

Desired Behavior

Provide an official plugin configuration setting or supported attribute (e.g. data-optml-keep-sizes or a global setting 'Preserve existing sizes attributes') so site administrators can prevent Optimole from overwriting manually defined HTML sizes attributes.

Acceptance Criteria
  • Add a setting in Optimole options or support a specific HTML data attribute to skip sizes attribute replacement.
  • When active/present, Optimole's HTML tag parser leaves existing sizes attributes untouched.
  • Include unit test coverage verifying pre-existing sizes attributes are preserved when the setting or attribute is present.

Customer Context

The customer has hand-crafted sizes attributes on photography listings and hero images. Optimole overwrites these with inaccurate profiler-generated slot measurements. The customer asks for an official setting or supported attribute to preserve existing sizes attributes without relying on calc() workarounds.

Root Cause Analysis

The customer manages an image-centric photography site and encountered multiple issues stemming from Optimole's automated HTML replacement and page profiler logic: 1) Optimole automatically overwrites HTML sizes attributes with measured slot widths unless explicit CSS functions like calc() are detected, leaving site authors who create custom responsive sizes attributes without a supported setting to preserve their HTML markup. 2) Profiled srcset candidate generation applies DPR transformations in a way that causes candidate descriptors to mismatch delivered image intrinsic widths when Retina Quality is active. 3) Page Profiler slot extrapolation calculates incorrect viewport slot widths on mobile layouts. 4) Duplicate max-width conditions are generated in sizes strings. 5) Database queries executed during the output buffer shutdown callback trigger MySQL 'Commands out of sync' errors. While issues #1111-#1114 address the specific bug regressions, an official setting/option to preserve existing sizes attributes fulfills an unaddressed gap in product configuration.

Reasoning

The customer conversation contains 5 distinct filable requests/reports: 1) Request for an official configuration option or mechanism to preserve pre-existing HTML sizes attributes on images rather than having Optimole overwrite them (new_feature_request). 2) Bug report that profiled srcset width descriptors mismatch delivered intrinsic image widths when Retina Quality is enabled, already tracked in GitHub issue #1111 (already_exists_github). 3) Bug report regarding inaccurate responsive slot widths extrapolated by Page Profiler, already tracked in issue #1112 (already_exists_github). 4) Bug report regarding duplicate max-width conditions in generated sizes attributes, already tracked in issue #1113 (already_exists_github). 5) Bug report regarding MySQL 'Commands out of sync' errors caused by PageProfiler transient reads during shutdown, already tracked in issue #1114 (already_exists_github). The top-level decision reflects the new, actionable feature request.

Source: HelpScout #3424946418
Generated by feature-request-triage workflow (ID: feature-request-triage_6a8821dfeacaf1.56068976)

Lenguaje dominante
PHP
Estrellas
73
Forks
14
Merge medio
2 d 13 h
PR fusionados (30 d)
16

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Codeinwp/optimole-wp

Todos los issues de Codeinwp/optimole-wp

Issues similares

Más issues de PHP

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.