X
Нажмите здесь, чтобы перейти на мобильную версию сайта.

Форум поддержки

Line breaks not copy/pasting from one site to another

Размещено

Sometime around the installation of 69.0 on my machine this month, the following weird problem has come up:

I will often compose text in a gmail draft message (gmail's autosave protects me from losing my work). Then when finished and proofed, I'll copy/paste the text into another buffer in my browser.

This worked straightforward as expected for more than a decade. But since 69.0, sometimes, in some sites (LinkedIn messaging is one example), the line breaks between paragraphs (entered, as would be expected, by pressing the enter key twice) are missing - there's only one line break, not two, after a paragraph.

Oddly, if I fix the line spacing in the non-gmail site, copy the result, then paste to gmail, anything I copy from that (what I've pasted back to gmail) then copy/pastes fine in the non-gmail site.

I've looked into this being a gmail problem, but I suspect that since the only thing that has changed for me in the past 10 days is a new FF version, it's a FF problem and not gmail.

This incidentally happens to me on two different computers - one is Windows 7, the other Windows 10.

Sometime around the installation of 69.0 on my machine this month, the following weird problem has come up: I will often compose text in a gmail draft message (gmail's autosave protects me from losing my work). Then when finished and proofed, I'll copy/paste the text into another buffer in my browser. This worked straightforward as expected for more than a decade. But since 69.0, sometimes, in some sites (LinkedIn messaging is one example), the line breaks between paragraphs (entered, as would be expected, by pressing the enter key twice) are missing - there's only one line break, not two, after a paragraph. Oddly, if I fix the line spacing in the non-gmail site, copy the result, then paste to gmail, anything I copy from that (what I've pasted back to gmail) then copy/pastes fine in the non-gmail site. I've looked into this being a gmail problem, but I suspect that since the only thing that has changed for me in the past 10 days is a new FF version, it's a FF problem and not gmail. This incidentally happens to me on two different computers - one is Windows 7, the other Windows 10.
Цитата

Дополнительные сведения о системе

Установленные плагины

  • Shockwave Flash 32.0 r0

Приложение

  • Firefox 69.0
  • User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0
  • URL поддержки: https://support.mozilla.org/1/firefox/69.0/WINNT/en-US/

Расширения

  • Adblock Plus - free ad blocker 3.6.3 ({d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d})
  • Amazon.com 1.1 (amazondotcom@search.mozilla.org)
  • Anti-Paywall 0.9.2 ({e5322648-dfe4-4c45-b02d-44c61d545f2b})
  • Bing 1.0 (bing@search.mozilla.org)
  • Bypass Paywalls 1.4.3 (iamadamdev@hotmail.com)
  • DuckDuckGo 1.0 (ddg@search.mozilla.org)
  • eBay 1.0 (ebay@search.mozilla.org)
  • Google 1.0 (google@search.mozilla.org)
  • mSession Keeper 0.8 (multi-session-keeper@pmorzonek)
  • Pushbullet 344 (jid1-BYcQOfYfmBMd9A@jetpack)
  • Twitter 1.0 (twitter@search.mozilla.org)
  • Video DownloadHelper 7.3.7 ({b9db16a4-6edc-47ec-a1f4-b86292ed211d})
  • Wikipedia (en) 1.0 (wikipedia@search.mozilla.org)
  • BugMeNot Plugin 3.1-signed.1-signed ({987311C6-B504-4aa2-90BF-60CC49808D42}) (Неактивно)
  • Custom Tab Width 1.0.1.1-signed.1-signed (tab-width@design-noir.de) (Неактивно)
  • FlashStopper 2.5.0 (flashstopper@byo.co.il) (Неактивно)
  • IE View 1.5.6.1-signed.1-signed ({6e84150a-d526-41f1-a480-a67d3fed910d}) (Неактивно)
  • oldbar 1.2.1-signed.1-signed ({46868735-c3fa-47ce-8ce7-cce51a66aceb}) (Неактивно)

Javascript

  • incrementalGCEnabled: True

Графика

  • adapterDescription: Intel(R) HD Graphics
  • adapterDescription2:
  • adapterDeviceID: 0x0042
  • adapterDeviceID2:
  • adapterDrivers: igdumd64 igd10umd64 igdumdx32 igd10umd32
  • adapterDrivers2:
  • adapterRAM: Unknown
  • adapterRAM2:
  • adapterSubsysID: 00000000
  • adapterSubsysID2:
  • adapterVendorID: 0x8086
  • adapterVendorID2:
  • clearTypeParameters: Gamma: 2.2 Pixel Structure: RGB ClearType Level: 50 Enhanced Contrast: 50
  • contentUsesTiling: False
  • crashGuards: [{u'prefName': u'gfx.crash-guard.status.glcontext', u'type': u'glcontext'}]
  • direct2DEnabled: True
  • directWriteEnabled: True
  • directWriteVersion: 6.2.9200.22807
  • driverDate: 7-31-2012
  • driverDate2:
  • driverVendor:
  • driverVendor2:
  • driverVersion: 8.15.10.2827
  • driverVersion2:
  • featureLog: {u'fallbacks': [{u'message': u'Unsupported by driver', u'name': u'NO_CONSTANT_BUFFER_OFFSETTING'}], u'features': [{u'status': u'available', u'description': u'Compositing', u'log': [{u'status': u'available', u'type': u'default'}], u'name': u'HW_COMPOSITING'}, {u'status': u'available', u'description': u'Direct3D11 Compositing', u'log': [{u'status': u'available', u'type': u'default'}], u'name': u'D3D11_COMPOSITING'}, {u'status': u'available', u'description': u'Direct2D', u'log': [{u'status': u'available', u'type': u'default'}], u'name': u'DIRECT2D'}, {u'status': u'available', u'description': u'Direct3D11 hardware ANGLE', u'log': [{u'status': u'available', u'type': u'default'}], u'name': u'D3D11_HW_ANGLE'}, {u'status': u'available', u'description': u'GPU Process', u'log': [{u'status': u'available', u'type': u'default'}], u'name': u'GPU_PROCESS'}, {u'status': u'opt-in', u'description': u'WebRender', u'log': [{u'status': u'opt-in', u'message': u'WebRender is an opt-in feature', u'type': u'default'}], u'name': u'WEBRENDER'}, {u'status': u'blacklisted', u'description': u'WebRender qualified', u'log': [{u'status': u'available', u'type': u'default'}, {u'status': u'blacklisted', u'message': u'No qualified hardware', u'type': u'env'}], u'name': u'WEBRENDER_QUALIFIED'}, {u'status': u'available', u'description': u'Off Main Thread Painting', u'log': [{u'status': u'available', u'type': u'default'}], u'name': u'OMTP'}, {u'status': u'available', u'description': u'Advanced Layers', u'log': [{u'status': u'available', u'type': u'default'}, {u'status': u'available', u'message': u'Enabled for Windows 7 via user-preference', u'type': u'user'}], u'name': u'ADVANCED_LAYERS'}]}
  • info: {u'AzureContentBackend (UI Process)': u'skia', u'CMSOutputProfile': u'10144 bytes, too large', u'AzureCanvasBackend (UI Process)': u'skia', u'ApzWheelInput': 1, u'ApzDragInput': 1, u'ApzKeyboardInput': 1, u'AzureFallbackCanvasBackend (UI Process)': u'none', u'ApzAutoscrollInput': 1, u'AzureCanvasBackend': u'direct2d 1.1', u'AzureContentBackend': u'direct2d 1.1'}
  • isGPU2Active: False
  • numAcceleratedWindows: 3
  • numTotalWindows: 3
  • offMainThreadPaintEnabled: True
  • offMainThreadPaintWorkerCount: 3
  • targetFrameRate: 60
  • usesTiling: False
  • webgl1DriverExtensions: GL_ANGLE_client_arrays GL_ANGLE_depth_texture GL_ANGLE_explicit_context GL_ANGLE_explicit_context_gles1 GL_ANGLE_framebuffer_blit GL_ANGLE_framebuffer_multisample GL_ANGLE_instanced_arrays GL_ANGLE_lossy_etc_decode GL_ANGLE_memory_size GL_ANGLE_multi_draw GL_ANGLE_pack_reverse_row_order GL_ANGLE_program_cache_control GL_ANGLE_provoking_vertex GL_ANGLE_request_extension GL_ANGLE_robust_client_memory GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_ANGLE_texture_usage GL_ANGLE_translated_shader_source GL_CHROMIUM_bind_generates_resource GL_CHROMIUM_bind_uniform_location GL_CHROMIUM_color_buffer_float_rgb GL_CHROMIUM_color_buffer_float_rgba GL_CHROMIUM_copy_compressed_texture GL_CHROMIUM_copy_texture GL_CHROMIUM_sync_query GL_EXT_blend_func_extended GL_EXT_blend_minmax GL_EXT_color_buffer_half_float GL_EXT_debug_marker GL_EXT_discard_framebuffer GL_EXT_disjoint_timer_query GL_EXT_draw_buffers GL_EXT_float_blend GL_EXT_frag_depth GL_EXT_instanced_arrays GL_EXT_map_buffer_range GL_EXT_occlusion_query_boolean GL_EXT_read_format_bgra GL_EXT_robustness GL_EXT_sRGB GL_EXT_shader_texture_lod GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_s3tc_srgb GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_EXT_texture_rg GL_EXT_texture_storage GL_EXT_unpack_subimage GL_KHR_debug GL_KHR_parallel_shader_compile GL_KHR_robust_buffer_access_behavior GL_NV_EGL_stream_consumer_external GL_NV_fence GL_NV_pack_subimage GL_NV_pixel_buffer_object GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth32 GL_OES_element_index_uint GL_OES_get_program_binary GL_OES_mapbuffer GL_OES_packed_depth_stencil GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_surfaceless_context GL_OES_texture_border_clamp GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_array_object OES_compressed_EAC_R11_signed_texture OES_compressed_EAC_R11_unsigned_texture OES_compressed_EAC_RG11_signed_texture OES_compressed_EAC_RG11_unsigned_texture OES_compressed_ETC2_RGB8_texture OES_compressed_ETC2_RGBA8_texture OES_compressed_ETC2_punchthroughA_RGBA8_texture OES_compressed_ETC2_punchthroughA_sRGB8_alpha_texture OES_compressed_ETC2_sRGB8_alpha8_texture OES_compressed_ETC2_sRGB8_texture
  • webgl1Extensions: ANGLE_instanced_arrays EXT_blend_minmax EXT_color_buffer_half_float EXT_disjoint_timer_query EXT_float_blend EXT_frag_depth EXT_shader_texture_lod EXT_sRGB EXT_texture_filter_anisotropic OES_element_index_uint OES_standard_derivatives OES_texture_float OES_texture_float_linear OES_texture_half_float OES_texture_half_float_linear OES_vertex_array_object WEBGL_color_buffer_float WEBGL_compressed_texture_s3tc WEBGL_compressed_texture_s3tc_srgb WEBGL_debug_renderer_info WEBGL_debug_shaders WEBGL_depth_texture WEBGL_draw_buffers WEBGL_lose_context
  • webgl1Renderer: Google Inc. -- ANGLE (Intel(R) HD Graphics Direct3D11 vs_4_0 ps_4_0)
  • webgl1Version: OpenGL ES 2.0 (ANGLE 2.1.0.21dccd386996)
  • webgl1WSIInfo: EGL_VENDOR: Google Inc. (adapter LUID: 000000000000a70a) EGL_VERSION: 1.4 (ANGLE 2.1.0.21dccd386996) EGL_EXTENSIONS: EGL_EXT_create_context_robustness EGL_ANGLE_d3d_share_handle_client_buffer EGL_ANGLE_d3d_texture_client_buffer EGL_ANGLE_surface_d3d_texture_2d_share_handle EGL_ANGLE_query_surface_pointer EGL_ANGLE_window_fixed_size EGL_ANGLE_keyed_mutex EGL_ANGLE_surface_orientation EGL_NV_post_sub_buffer EGL_KHR_create_context EGL_EXT_device_query EGL_KHR_image EGL_KHR_image_base EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_get_all_proc_addresses EGL_KHR_stream EGL_KHR_stream_consumer_gltexture EGL_NV_stream_consumer_gltexture_yuv EGL_ANGLE_flexible_surface_compatibility EGL_ANGLE_stream_producer_d3d_texture EGL_ANGLE_create_context_webgl_compatibility EGL_CHROMIUM_create_context_bind_generates_resource EGL_EXT_pixel_format_float EGL_KHR_surfaceless_context EGL_ANGLE_display_texture_share_group EGL_ANGLE_create_context_client_arrays EGL_ANGLE_program_cache_control EGL_ANGLE_robust_resource_initialization EGL_ANGLE_create_context_extensions_enabled EGL_ANDROID_blob_cache EGL_ANDROID_recordable EGL_EXTENSIONS(nullptr): EGL_EXT_client_extensions EGL_EXT_platform_base EGL_EXT_platform_device EGL_ANGLE_platform_angle EGL_ANGLE_platform_angle_d3d EGL_ANGLE_device_creation EGL_ANGLE_device_creation_d3d11 EGL_ANGLE_experimental_present_path EGL_KHR_client_get_all_proc_addresses EGL_KHR_debug EGL_ANGLE_explicit_context
  • webgl2DriverExtensions: -
  • webgl2Extensions: -
  • webgl2Renderer: WebGL creation failed: * tryANGLE * Exhausted GL driver options.
  • webgl2Version: -
  • webgl2WSIInfo: -
  • windowLayerManagerRemote: True
  • windowLayerManagerType: Direct3D 11
  • windowUsingAdvancedLayers: True

Изменённые настройки

Разное

  • User JS: Нет
  • Доступность: Нет
jscher2000
  • Top 10 Contributor
8695 решений 71071 ответов
Размещено

Hi firefoxacct.10.dggeorge, I'm not aware of a new change related to line breaks, but let me mention an older one:

There was a change in Firefox 60 that made Firefox more like other browsers, which conflicts with how the editors on some sites treat Firefox specially. You could try the following change to see whether it affects LinkedIn:

(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful or accepting the risk.

(2) In the search box above the list, type or paste newline and pause while the list is filtered

(3) Double-click the editor.use_div_for_default_newlines preference to switch the value from true to false (was false in Firefox 57-59)

Any difference on either side (Gmail or LinkedIn)?

Hi firefoxacct.10.dggeorge, I'm not aware of a new change related to line breaks, but let me mention an older one: There was a change in Firefox 60 that made Firefox more like other browsers, which conflicts with how the editors on some sites treat Firefox specially. You could try the following change to see whether it affects LinkedIn: (1) In a new tab, type or paste '''about:config''' in the address bar and press Enter/Return. Click the button promising to be careful or accepting the risk. (2) In the search box above the list, type or paste '''newline''' and pause while the list is filtered (3) Double-click the '''editor.use_div_for_default_newlines''' preference to switch the value from true to false (was false in Firefox 57-59) Any difference on either side (Gmail or LinkedIn)?
Помогла ли вам это?
Цитата
Размещено

Задавший вопрос

jscher2000 said

Hi firefoxacct.10.dggeorge, I'm not aware of a new change related to line breaks, but let me mention an older one: There was a change in Firefox 60 that made Firefox more like other browsers, which conflicts with how the editors on some sites treat Firefox specially. You could try the following change to see whether it affects LinkedIn: (1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful or accepting the risk. (2) In the search box above the list, type or paste newline and pause while the list is filtered (3) Double-click the editor.use_div_for_default_newlines preference to switch the value from true to false (was false in Firefox 57-59) Any difference on either side (Gmail or LinkedIn)?

Thanks. This was a great guess. Unfortunately, this didn't solve the problem. the preference you mentioned was true when I entered about:config, I switched it to false, but doing so didn't fix things. Best I can tell, it didn't change anything.

''jscher2000 [[#answer-1250442|said]]'' <blockquote> Hi firefoxacct.10.dggeorge, I'm not aware of a new change related to line breaks, but let me mention an older one: There was a change in Firefox 60 that made Firefox more like other browsers, which conflicts with how the editors on some sites treat Firefox specially. You could try the following change to see whether it affects LinkedIn: (1) In a new tab, type or paste '''about:config''' in the address bar and press Enter/Return. Click the button promising to be careful or accepting the risk. (2) In the search box above the list, type or paste '''newline''' and pause while the list is filtered (3) Double-click the '''editor.use_div_for_default_newlines''' preference to switch the value from true to false (was false in Firefox 57-59) Any difference on either side (Gmail or LinkedIn)? </blockquote> Thanks. This was a great guess. Unfortunately, this didn't solve the problem. the preference you mentioned was true when I entered about:config, I switched it to false, but doing so didn't fix things. Best I can tell, it didn't change anything.
Помогла ли вам это?
Цитата
cor-el
  • Top 10 Contributor
  • Moderator
17478 решений 157953 ответов
Размещено

Did you check the HTML code that you get when pasting the text assuming that this is a rich text editor (WYSIWYG)?

Did you check the HTML code that you get when pasting the text assuming that this is a rich text editor (WYSIWYG)?
Помогла ли вам это?
Цитата
Размещено

Задавший вопрос

cor-el said

Did you check the HTML code that you get when pasting the text assuming that this is a rich text editor (WYSIWYG)?

I haven't. Is there generated html code simply when pasting into a buffer (versus "posting" or sending the text)? If so, how would I check it?

I will say, other than the FF version, nothing here has changed. "Expected" behavior was the norm for my dozen years with FF and gmail. It's only been this month that the unexpected behavior started.

''cor-el [[#answer-1250459|said]]'' <blockquote> Did you check the HTML code that you get when pasting the text assuming that this is a rich text editor (WYSIWYG)? </blockquote> I haven't. Is there generated html code simply when pasting into a buffer (versus "posting" or sending the text)? If so, how would I check it? I will say, other than the FF version, nothing here has changed. "Expected" behavior was the norm for my dozen years with FF and gmail. It's only been this month that the unexpected behavior started.
Помогла ли вам это?
Цитата
cor-el
  • Top 10 Contributor
  • Moderator
17478 решений 157953 ответов
Размещено

Some websites may have changed from a plain text editor to a rich text editor that accepts HTML formatting code like <P> tags and <DIV> tags as block element and <SPAN> tags for inline text and tags to style the text (bold: <B>; italic: <I>; underline: <U>). A Rich text editor usually has a tab to switch to plain text mode to inspect the HTML code.

Some websites may have changed from a plain text editor to a rich text editor that accepts HTML formatting code like &lt;P&gt; tags and &lt;DIV&gt; tags as block element and &lt;SPAN&gt; tags for inline text and tags to style the text (bold: &lt;B&gt;; italic: &lt;I&gt;; underline: &lt;U&gt;). A Rich text editor usually has a tab to switch to plain text mode to inspect the HTML code.
Помогла ли вам это?
Цитата
Размещено

Задавший вопрос

I don't know if this is related, but I just posted a new question about unwanted line breaks: https://support.mozilla.org/en-US/questions/1268823

To summarize, now in composing in gmail - only in Firefox - pressing "enter" generates a <br> tag, but after entering a numbered or bulleted list, pressing "enter" generates a <p> tag.

I don't know if this is related, but I just posted a new question about unwanted line breaks: https://support.mozilla.org/en-US/questions/1268823 To summarize, now in composing in gmail - only in Firefox - pressing "enter" generates a &lt;br&gt; tag, but after entering a numbered or bulleted list, pressing "enter" generates a &lt;p&gt; tag.

Изменено cor-el

Помогла ли вам это?
Цитата
jscher2000
  • Top 10 Contributor
8695 решений 71071 ответов
Размещено

firefoxacct.10.dggeorge said

To summarize, now in composing in gmail - only in Firefox - pressing "enter" generates a <br> tag, but after entering a numbered or bulleted list, pressing "enter" generates a <p> tag.

You could undo the change to the editor.use_div_for_default_newlines preference from earlier in this thread and see whether that resolves the Gmail issue.

''firefoxacct.10.dggeorge [[#answer-1252001|said]]'' <blockquote>To summarize, now in composing in gmail - only in Firefox - pressing "enter" generates a <code>&lt;br></code> tag, but after entering a numbered or bulleted list, pressing "enter" generates a <code>&lt;p></code> tag. </blockquote> You could undo the change to the '''editor.use_div_for_default_newlines''' preference from earlier in this thread and see whether that resolves the Gmail issue.
Помогла ли вам это?
Цитата
Размещено

Задавший вопрос

jscher2000 said

firefoxacct.10.dggeorge said
To summarize, now in composing in gmail - only in Firefox - pressing "enter" generates a <br> tag, but after entering a numbered or bulleted list, pressing "enter" generates a <p> tag.

You could undo the change to the editor.use_div_for_default_newlines preference from earlier in this thread and see whether that resolves the Gmail issue.

I appreciate your re-reminding me of this.

The suggestion fixed a different problem I posted in a later thread (gmail going to double-line-spacing after a numbered or bullet list).

But I tried for this problem, and this suggestion did not fix this problem.

''jscher2000 [[#answer-1252005|said]]'' <blockquote> ''firefoxacct.10.dggeorge [[#answer-1252001|said]]'' <blockquote>To summarize, now in composing in gmail - only in Firefox - pressing "enter" generates a <code>&lt;br></code> tag, but after entering a numbered or bulleted list, pressing "enter" generates a <code>&lt;p></code> tag. </blockquote> You could undo the change to the '''editor.use_div_for_default_newlines''' preference from earlier in this thread and see whether that resolves the Gmail issue. </blockquote> I appreciate your re-reminding me of this. The suggestion fixed a different problem I posted in a later thread (gmail going to double-line-spacing after a numbered or bullet list). But I tried for this problem, and this suggestion did not fix this problem.
Помогла ли вам это?
Цитата
jscher2000
  • Top 10 Contributor
8695 решений 71071 ответов
Размещено

gamma45 said

But I tried for this problem, and this suggestion did not fix this problem.

Yes, I remember. This problem is unsolved. (I don't want to experiment with my personal LinkedIn account.)

''gamma45 [[#answer-1252014|said]]'' <blockquote> But I tried for this problem, and this suggestion did not fix this problem. </blockquote> Yes, I remember. This problem is unsolved. (I don't want to experiment with my personal LinkedIn account.)
Помогла ли вам это?
Цитата
Задать вопрос

Для ответа на сообщения вы должны войти в свою учётную запись. Пожалуйста, задайте новый вопрос, если у вас ещё нет учётной записи.